I have an Laravel application, and I use Rocketeer to deploy the app. After deploy
It showing that the symlink is actually pointed to the latest release, but then, when I refresh the page, it still refer to the older release.
I really have no idea what is going on. Because this issue doesn't happen in DigitalOcean as well as other hosting.
Please help
Related
I have created a django website which now I am looking to deploy through DigitalOcean, I have not uploaded it yet because I want to get a clear picture before actually starting.
My questions are,
How to I update the packages required for my website once I have deployed my website?
Eg: I am using CKEditor 6. In future, when CKEditor 7 arrives how do I update the package so that my
website uses the latest CKEditor without losing any data.
DigitalOcean deployment works with and without git right? So should I skip git, because I really do not
care about versioning my website. Simple update through FTP apps(WinSCP, Filezilla) will work for me.
Generally speaking remote server is no different from a local machine what stays in your bedroom. Yes, it doesn't have monitor, yes, it is a rack with a lot of wires and yes, it is usually far away from you, but afterall the logic is the same. Thus everything works almost the same way it does on your local computer. Yes, you will be able to update dependencies, yes you will be able to not use git. But the fact you may not use git, doesn't mean that you should not. Also you will have to think of another DB, proxy server and intermediary between such and django app.
I use Java APIs for the CRUD operations of the google cloud deployment manager API. I can create, preview, delete deployments OK.
But when I try to update an existing deployment that's in preview mode, the API returns the below error.
Deployment in preview must not have a target with UPDATE
The same inputs works OK for create and preview. So, I'm sure that the inputs are OK.
I looked up for others who have reported this issue.
Here is one such report but no solution.
Does anyone know if there's a git hub repo for google cloud deployment manager where we can report this issue?
As mentioned in the answer here, is a known issue and you can still use the workaround suggested.
I have created an issue tracker for this error message. So, you can add your comments there and follow up for upcoming updates.
I am a novice when it comes to deploying website. I have set up an EC2 instance and linked it to my domain. I proceeded to install Apache and I have obtained this result when I open my domain in browser.
implying I have done everything right until here.
Where do I go from here? I don't have prior linux experience one of the reasons for my situation. I need to deploy the cakephp project I have created.
I apologies for the rather broad question, it was only very recently that I learned to code.
Cakephp has a detailed documentation on how to install and configure cakephp.
https://book.cakephp.org/3.0/en/installation.html
I am trying to follow the instructions on this page, and they are working great, until the part where I deploy from my Google App Engine Launcher. When I click deploy I should see something like this:
But instead, I see something like this:
and the end result is that my app doesn't get deployed to xxxxxxx.appspot.com, it redirects me to http://localhost:8080/?code=4/EfmizPdAPVDgoSInA8mS1KVOvQTkWX4ziFnEpG3XKxA#
I'm a begginer with this kind of tech, please, any suggestions on how to troubleshoot?
Found the answer here. In my case, what worked was to first disable the app in the App Engine Launcher, and only then hit deploy. First time I tried, it authenticated, then second time I deployed, it deployed successfully. Thanks Arnie.
In case, I post his other suggestions:
1) remember to give your google id access to less secure apps.
2) remember to go to appspot.com or https://appengine.google.com/ and accept terms and conditions. Your project should also be active on https://console.developers.google.com/project
3) use correct versions of python and google app engine SDK
4) Before hitting deploy button on google app engine stop the app from running on your local host. It will NOT deploy while it is running locally on local host.
I have deployed rails spree app to AWS Beanstalk successfully. Then I added some new products together with their images. The app by default saves the images in my_app/public/spree/products folder. Every thing went fine until I deployed new code. The new code is deployed successfully but the "products" folder is gone. I now have to re-upload all of my images manually. Anyone has any idea what is going here?
Please let me know if you need any further info.
Thanks!!
Application will contain a public folder and under of this, we have spree products/taxons images folder...Those files are static by nature, so it’s a good idea to serve them using S3 because for every deployment our code replace.
Elastic beanstalk servers are somehow out of your control, meaning AWS controls when they are restarted and even terminated and rebuilt. Therefore, you shouldn't store anything on local disks (which is what Spree does by default).
The solution to your problem is simply to store them on S3 as described here.