Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
You need to restart Unicorn. Until you restart, the old files will still show.
service unicorn restart
As long as you put your new project in /home/rails/rails_project, you don’t need to change anything on the server, assuming you are using the 1-click Rails App image.
It sounds like the issue that your hitting is related to the Nginx configuration on the droplet. In order for Nginx to know about the new location of your Rails app you will need to update the config file located at /etc/nginx/sites-enabled/rails.
Along with updating the Nginx configuration, the Unicorn config file will need to updated as well. The Unicorn config file can be found at ```/etc/unicorn.conf`
Don’t forget to restart the services to load the new configuration.