rtcwake. See below for step by step:
$ sudo su $ crontab -e
crontab.# Shutdown at 12 AM and awake afer 8 hours (8:00 AM) 0 0 * * * sudo /usr/sbin/rtcwake -m disk -s 28800 > /var/log/crontab.log
sudo apt-get update sudo apt-get install samba
sudo smbpasswd -a <user_name>Note: Samba uses a separate set of passwords than the standard Linux system accounts (stored in /etc/samba/smbpasswd). Having said that, I always use here whatever username I use for my Linux account.
mkdir /home/<user_name>/<folder_name>
sudo vim /etc/samba/smb.confAnd add the following:
[global] workgroup = HOME_NETWORK #(Set this to the name you want the shared folder to have) [share] comment = File server share folder path = /home/<user_name>/share/ browsable = yes read only = no guest ok = yes writable = yes valid users = <samba_user_name> create mask = 0755
ufw allow 445
sudo service smbd restart
testparm
sudo apt-get update
sudo apt-get install mysql-server
sudo mysql_secure_installation
sudo mysql_install_db
gem 'pry-remote', '~> 0.1.8'
gem 'pry-nav', '~> 0.2.4'
require 'pry-remote'
binding.remote_pry
pry-remote
step
next
continue
exit
git clone git@bitbucket.org:kabalweg/app_name.git cd app_name bundle installIf you get a "bundle not yet installed" error, run the following comment:
gem install bundle
sudo ln -s /home/kabalweg/app_name/ ./app_name
<VirtualHost *:80>
ServerName app_name.net
Redirect permanent / http://www.app_name.net/
</VirtualHost>
<VirtualHost *:80>
ServerName www.app_name.net
ServerAdmin kabalweg@gmail.com
# Set the environment to production
RailsEnv production
<IfModule mod_passenger.c>
# Set to on when debugging errors
PassengerFriendlyErrorPages off
#PassengerRoot /usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini
#PassengerDefaultRuby /home/kabalweg/.rvm/gems/ruby-2.2.1@rails4.2/wrappers/ruby
PassengerMaxPoolSize 2
PassengerPoolIdleTime 0
PassengerMaxRequests 1000
</IfModule>
DocumentRoot /var/www/app_name/public
<Directory /var/www/app_name/public>
AllowOverride all
Options -MultiViews
#Require all granted
Order deny,allow
Allow from all
</Directory>
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
sudo a2dissite 000-default.conf sudo a2ensite app_name.conf sudo apachectl -k graceful
rake secret RAILS_ENV=productionNote: It's not a good and safe practice to put production config values in the repo. A good way is to ignore config files (*.yml) using git so it don't get save in the repo, then just manually create this files, with the correct values, in the production server.
rake assets:precompile RAILS_ENV=production
touch tmp/restart.txtCreate this folder (tmp) if you don't have this.
sudo apt-get update sudo apt-get install apache2
sudo vim /etc/apache2/apache2.confand enter at the end of the file:
ServerName server_domain_or_IP
sudo apache2ctl configtest
sudo systemctl restart apache2
# Install our PGP key and add HTTPS support for APT sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 561F9B9CAC40B2F7 sudo apt-get install -y apt-transport-https ca-certificates # Add our APT repository sudo sh -c 'echo deb https://oss-binaries.phusionpassenger.com/apt/passenger xenial main > /etc/apt/sources.list.d/passenger.list' sudo apt-get update # Install Passenger + Apache module sudo apt-get install -y libapache2-mod-passengerThese commands will install Passenger + Apache module through Phusion's APT repository.
sudo a2enmod passenger sudo apache2ctl restart
sudo passenger-config validate-installAll checks should pass. If any of the checks do not pass, please follow the suggestions on screen.
sudo passenger-memory-stats
$ rails new [app_name] --skip-active-record --skip-test-unit
$ rails generate controller main_controller index --no-assets --no-helper
root 'main_controller#index'
passwdIt's always good to use a strong root password. I recommend Random Password Generator for this.
apt-get update apt-get upgrade
apt-get install fail2banFail2ban is a daemon that monitors login attempts to a server and blocks suspicious activity as it occurs. It’s well configured out of the box.
useradd deploy mkdir /home/deploy mkdir /home/deploy/.ssh chmod 700 /home/deploy/.ssh
sudo chsh -s /bin/bash deploy
vim /home/deploy/.ssh/authorized_keysCopy and paste the contents of the id_rsa.pub on your local machine and any other public keys that you want to have access to this server to the
/home/deploy/.ssh/authorized_keys file. Save and close the file.
chmod 400 /home/deploy/.ssh/authorized_keys chown deploy:deploy /home/deploy -R
ssh deploy@<IP_OF_DROPLET>
deploy, generate SSH key. This will be used when connecting to github or bitbucket
ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
exit
passwd deploy
update-alternatives --config editor
visudoAdd the following line:
root ALL=(ALL:ALL) ALL deploy ALL=(ALL:ALL) ALLThis will grant sudo access to the deploy user when they enter the proper password.
ufw allow 22 ufw allow 80 ufw allow 443 ufw enable
apt-get install unattended-upgrades vim /etc/apt/apt.conf.d/10periodicUpdate the file to look like this:
APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "7"; APT::Periodic::Unattended-Upgrade "1";One more config file to edit:
vim /etc/apt/apt.conf.d/50unattended-upgradesUpdate the file to look like below. This will enable security updates only:
Unattended-Upgrade::Allowed-Origins {
"Ubuntu lucid-security";
// "Ubuntu lucid-updates";
};
or
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
};
reboot
