Quick and easy way to setup Codedeploy for CodeIgniter on Bitbucket? - codeigniter

Can someone please direct me to a simple, quick and easy way to setup a CodeIgniter project (hosted via Bitbucket) with AWS CodeDeploy?

Related

Best practise/way to deploy Laravel + Vue SPA application to AWS

I have 2 repositories residing in Bitbucket - Backend (Laravel app as the API and entry point) and Frontend (Main application front-end - VueJs app). My goal is to set up continuous deployment so whenever something is pushed in either of the repos in master (or other branch selected by me) branch it triggers something so that the whole app builds and reaches the AWS EC2 server.
I have considered/tried the following:
AWS CodePipeline and/or CodeDeploy. This looked like a great option
since the servers are in AWS as well. However, there is no support
for Bitbucket out of the box, so it would have to go to Bitbucket
Pipeline -> AWS Lambda -> AWS S3 -> AWS CodePipeline/CodeDeploy ->
AWS EC2. This seems like a very lengthy journey and I am not sure if
that's a good practice whatsoever.
Using Laravel Forge to deploy the Laravel app, and add additional steps to build the VueJS app. This seemed like a very basic solution,
however, the build process seems to fail there as it just takes long
time and crashes with no errors (whereas I can run exact same process
on my local machine or a different server hosted elsewhere). I am not
sure if this is issue with the way server is provisioned, the way
Forge runs deployment script or the server is too weak to handle it.
The main question of mine would be what are the best pracises for deploying the app of such components? I have read many tutorials/articles about deploying a NodeJS app, or a Laravel app, but haven't gotten good information about a scenario like this.
Would it be better to build the front-end app locally and version control the built JS file? Or should I create a Pipeline in Bitbucket that would build the app and then deploy it? Or is it the best to just version control and deploy the source files and leave the whole build process as the last step in the deployment process that will be done by the server that is hosting the app itself? There are also some articles suggesting hosting the whole front-end app in S3 bucket - would that be bad practise as well?
Appreciate any help and resources that would help!
From the sounds of things it sounds like you have two types of deployments you might want to run.
Laravel API: If you're using Laravel Forge already then this is a great way to go about deploying your Laravel App, takes care of most of the process and easy server management.
Vue.js App: Few things you can do here, I personally prefer using a provider like Vercel or Netlify who let you deploy your static sites/frontends for free-low costs. You can write custom build steps but they have great presets that should work out the box.
If you really want to keep everything on AWS then look into how to host static sites on AWS

Pros/Cons of Parse Dashboard local installation vs deployment

I wasn't able to find solid information on this and I wanted to ask developers who use Parse Dashboard:
What are the pros/cons of Parse Dashboard local installation vs deployment?
I currently run the Parse Dashboard on local installation, but I know that deployment to Heroku is also an option (my app is deployed on Heroku). I wanted to gather some information before deploying/not deploying.
Thank you!
I also have it running locally and I think for security reasons it's best to do so. If you setup the dashboard on the same server on which Parse is running, then you will have to take security measure to protect access to the dashboard and the config file which includes your masterkey and all that. This definitely outweighs the arguments to host it locally, which in my opinion only is that it's easier to access the dashboard.
If you really want to setup a dashboard on a server at least do it on a separate server.

How to deploy my website online

I have a website build using Codeigniter Framework. I already uploaded it in a web server, TurnKey Lamp in Linux using Git Bash.. I can access it already since it is networked.. What I want now is to make it visible on internet.. How can I do that?

How can I go about loading Mule ESB onto a AWS EC2?

I need to upload it to EC2 and am unsure how to go about it. I am using Eclipse with the Mule plugin.
Hi there have you try CloudHub?
It's basically Mule in the Cloud
You can simply follow the installation guide from the documentation and that should be it.
Please see:
http://www.mulesoft.org/documentation/display/current/Downloading+and+Installing+Mule+ESB#download-MuleCommunityRuntime
There's a ready made and up to date Docker container that can simplify things for you: https://registry.hub.docker.com/u/vromero/mule/
After starting the container, just drop your Mule application ZIPs into /opt/mule/apps.
There are other notable mount points: make sure to read the user guide to learn more.

Setting up codeship to deploy bitbucket repository to vidahost cloud hosting

I have a private bitbucket php project repository, codeship account and a vidahost cloud hosting. How to implement continuous integration and deployment? What is the workflow to achieve this? I did googling but could not find complete tutorial.
Ahoy Dipendra,
Marko from the Codeship crew here. Could you send me an in app message with a link to your project, so I can take a look at your current setup and help get you started?
As for deploying to Vidahost, you have multiple options. You could use a tool like Capistrano (or Mina, or something similar in your preferred programming language) or you could use SCP or FTP directly to copy your files. For the latter option, please see our documentation at https://codeship.com/documentation/continuous-deployment/deployment-with-ftp-sftp-scp/. (You'll find documentation on Capistrano and a bunch of other deployment options via this link as well.)
I'll update this answer with more specific details, once I know more about your setup!
Cheers,
Marko

Resources