Your Appwrite self-hosted platform uses the Docker network to isolate your container from the outside world.
As that, we first need to obtain the MariaDB internal IP. To find it run the following command on your server
$: docker network inspect appwrite_appwrite --format '{{range .Containers}}{{println .Name .IPv4Address println }}{{end}}' | grep mariadb
Your Appwrite self-hosted platform uses the Docker network to isolate your container from the outside world.
As that, we first need to obtain the MariaDB internal IP. To find it run the following command on your server
$: docker network inspect appwrite_appwrite --format '{{range .Containers}}{{println .Name .IPv4Address println }}{{end}}' | grep mariadb
| @next_upgrade ||= false | |
| source 'https://rubygems.org' | |
| if @next_upgrade | |
| gem 'rails', '6.0.0.rc2' | |
| else | |
| gem 'rails', '~> 5.2.0' | |
| end | |
| # rest of gems below .... |
| # unicorn_rails -c /data/github/current/config/unicorn.rb -E production -D | |
| rails_env = ENV['RAILS_ENV'] || 'production' | |
| # 16 workers and 1 master | |
| worker_processes (rails_env == 'production' ? 16 : 4) | |
| # Load rails+github.git into the master before forking workers | |
| # for super-fast worker spawn times | |
| preload_app true |
| # unicorn_rails -c /data/github/current/config/unicorn.rb -E production -D | |
| rails_env = ENV['RAILS_ENV'] || 'production' | |
| # 16 workers and 1 master | |
| worker_processes (rails_env == 'production' ? 16 : 4) | |
| # Load rails+github.git into the master before forking workers | |
| # for super-fast worker spawn times | |
| preload_app true |
| # Usage: | |
| # 1. Drop this file into lib/capistrano/remote_cache_with_project_root_strategy.rb | |
| # 2. Add the following to your Capfile: | |
| # require 'capistrano/git' | |
| # require './lib/capistrano/remote_cache_with_project_root_strategy' | |
| # 3. Add the following to your config/deploy.rb | |
| # set :git_strategy, RemoteCacheWithProjectRootStrategy | |
| # set :project_root, 'subdir/path' | |
| # Define a new SCM strategy, so we can deploy only a subdirectory of our repo. |
| # Guide | |
| # Configure the essential configurations below and do the following: | |
| # | |
| # Repository Creation: | |
| # cap deploy:repository:create | |
| # git add . | |
| # git commit -am "initial commit" | |
| # git push origin master | |
| # | |
| # Initial Deployment: |
| Latency Comparison Numbers | |
| -------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns | |
| Send 1K bytes over 1 Gbps network 10,000 ns 0.01 ms | |
| Read 4K randomly from SSD* 150,000 ns 0.15 ms |
| # Guide | |
| # Configure the essential configurations below and do the following: | |
| # | |
| # Repository Creation: | |
| # cap deploy:repository:create | |
| # git add . | |
| # git commit -am "initial commit" | |
| # git push origin master | |
| # | |
| # Initial Deployment: |