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.

So, I’ve got nginx up and running just fine, serving the main static site like I want it to. I’ve also got Ghost running just fine; if I plug in my site’s address and append :2368, I can look at the blog right now. Here’s how my zone file looks:
$ORIGIN landermkerbey.com.
$TTL 1800
landermkerbey.com. IN SOA ns1.digitalocean.com. hostmaster.landermkerbey.com. 1430683439 10800 3600 604800 1800
landermkerbey.com. 1800 IN A 162.243.45.221
landermkerbey.com. 1800 IN NS ns1.digitalocean.com.
landermkerbey.com. 1800 IN NS ns2.digitalocean.com.
landermkerbey.com. 1800 IN NS ns3.digitalocean.com.
*.landermkerbey.com. 1800 IN CNAME landermkerbey.com.
blog.landermkerbey.com. 1800 IN A 162.243.45.221
I have one nginx/sites-available file for both the main site and the blog, both of which have symbolic links in the sites-enabled directory. The one for the blog looks like this:
server {
listen 80 default_server;
listen [::]:80 default_server ipv6only=on;
server_name blog.landermkerbey.com;
access_log /var/log/nginx/ghost.log
client_max_body_size 10G;
location / {
proxy_pass http://localhost:2368;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_buffering off;
}
It also has a location /doc and location /images section, though those are unedited from the default file provided by nginx.
As for my config.js file, I went ahead and modified the production section:
// ### Production
// When running Ghost in the wild, use the production environment
// Configure your URL and mail settings here
production: {
url: 'http://blog.landermkerbey.com',
mail: {},
database: {
client: 'sqlite3',
connection: {
filename: path.join(__dirname, '/content/data/ghost.db')
},
debug: false
},
server: {
// Host to be passed to node's net.Server#listen()
host: '127.0.0.1',
// Port to be passed to node's net.Server#listen(), for iisnode set this to process.env.PORT
port: '2368'
}
},
So, what am I doing wrong? Should the blog and main site be contained in a single sites-available file?
009fd274aeae48f2bfbda6ef568676
Cloudstream Apk
Ruz
Ruz
Edward Sitarski
ebeecroft
dashan
34bcef38725b4e6eb5224ae028f17e
markatango
gouskova
Andrew J Montanus