javierm on clear_backspace
Create admin user before starti… (compare)
javierm on delete_comments
Allow users to delete their own… (compare)
javierm on docker_2.6
Use Ruby 2.6 in the Dockerfile … (compare)
javierm on fix_follow_cache
Avoid a brakeman security warni… Make sure users can only delete… Expire cache when users follow/… (compare)
javierm on sdg_serbian_icons
Add SDG icons for Serbian (Cyri… (compare)
javierm on restore_user_content
Small block user refactor Restore all related content whe… (compare)
javierm on install_rvm
Speed up deployment when Ruby i… (compare)
javierm on fix_flaky_dashboard_spec
Fix flaky spec "Edit poll allow… TEMPO (compare)
javierm on clear_backspace
Clear fields in tests before fi… (compare)
javierm on master
Move map_location attributes to… Allow to create an investment w… Make the do_login_for method ac… and 5 more (compare)
javierm on improve-management-investments
Hey @gildvir, @Rajendransiva
After making changes to the application configuration or code only Unicorn needs to be restarted.
Check out the next comment for details.
Hey @leog, @natasakvinfo
The best way to restart the Unicorn is to setup Capistrano and run a
cap production deploy:restart.
If you haven't setup Capistrano yet check out this issue:
Note the full command, without variables, to restart Unicorn manually would be:
cd /home/deploy/consul && /home/deploy/.rvm/gems/ruby-2.3.2/wrappers/unicorn -c config/unicorn.rb -E production -D
Apart from that we are adding the Unicorn script to the tasks to be executed after a server reboot.
In the meantime please use Capistrano to restart the Unicorn server or start it manually with the command above or add it to the crontab with these commands:
@reboot cd /home/deploy/consul && /home/deploy/.rvm/gems/ruby-2.3.2/wrappers/unicorn -c config/unicorn.rb -E production -D
sudo rebootand you should now see CONSUL running at your ip address in the browser after the server reboot.
Thank you for opening an issue about that one. Glad we got it working. :tada:
i am trying to extablish a lock from 2 process(each process from a differt pod). In first trail, 1 process(assume p1 process got the lock) is getting the lock succesfully. But when i try to kill & start the p1 process, the lock is not getting shiffting to the other process(p2) provided the p2 tries for every 5s. Niether process is getting the lock.
But in log i try to see the error as 'already started' in the both the process logs. When i check for the consul process in ps-ef , vain.
And if i try to stop the 2 process and start againg simatanouly, either one will get the lock and flaw goes again.
commad used "/tmp/consul lock -timeout 5s t1 " while :; do sleep 10; done"" FYI, i am tring in golang exec package as
cmd := "/tmp/consul lock -timeout 5s t1 \" while :; do sleep 10; done\""
aa := exec.Command("/bin/sh", "-c", cmd)
You might just be missing a
cap production deploy from your local machine: consul/installer#107
Regarding developing and deploying in the same environment, if you mean running CONSUL in the production environment in your local machine, sure, just add the environment option when starting the server:
bin/rails s -e production
The Gitter room you are searching for is: https://gitter.im/hashicorp-consul/Lobby
if you keep needing to make your local server available to your local network checkout this post https://stackoverflow.com/questions/29132719/rails-application-not-visible-to-local-network!
Hi @psalazar_gitlab, we have some documentation to help you with Docker, if you are not using Windows OS maybe you can find some useful information to make it work.