@lhl BTW, I heard that the free tier on Amazon EC2 runs out quickly. How many months have you been running your blog? If you are paying already then what is the cost. I need to be sure before I jump anywhere.
When I was using Bitbucket and an S3 instance where there is a lot of upload each time (I was using a HUGO Static Generated site at the time) my monthly costs were around $5 - $8 over the FREE allowance - roughly updating on a daily basis.
Now I am using WriteFreely, still updating once every few days or so, single user - based on a AWS EC2 instance, also using AWS Route53 to register my domain my monthly costs are approx $1.50.
For my usage it is less than when I was using VULTR to host my sites. A lot will depend on your usage environment.
One of the reasons I switched from HUGO to WriteFreely was the ease of administration. I still wanted a bare-bones blog with very few, if any, bells & whistles. I also wanted to really restrict the outgoing costs to the absolute minimum for a personal use only site that I have control over.
So, if I use Scaleway’s basic tier that costs around €1.99/mo (about $2.26) with 25GB SSD & 1 GB Memory but it has a minified version of Ubuntu 16.04, would you recommend me that?
I would think that there is not a lot of difference in most of the offers out there at this level of requirements. So long as you are not locking yourself into a minimum term contract - you can pretty much switch a VPS on/off as you please.
There is some effort required in backing-up files and db’s etc but it is always fairly easy to move from one provider to another if you find it doesn’t suit you.
I have uploaded writefreely folder directly to var/www and according I changed the two files you have mentioned like this:
Sorry, I don’t know. As I said I’m an average joe, not a developer or programmer. I think @matt can probably be much more useful to you to problem solve.
All I can see is that the ExecStart= in the writefreely.sevice file should read:
/var/www/example.com/writefreely as outlined in the Getting Started pages here
example.com should be replaced by the name of the folder you have used to store the files to.
If you are running the files from a reverse NGINX configuration check that your file PATH is correct first. NGINX also requires you to create a symlink to the WriteFreely files in order to be able to serve them. Again my experience of these things is generally through trial and error as I am doing them.
Can you show me these same files for your server? You can blur any sensitive details.
The writefreely.service and writefreely.conf are as in my original post (only changes are where I input specifics for my address) Not much to show really.
Have a look at this link first about how to set up a symlink with NGINX. It is for another software, but the information is useful: https://learn.getgrav.org/webservers-hosting/servers/nginx.
There should be very little different to your setup when using a
localhost. Is that not what you had set up…?
Yes. But it was development and not production. That too in Windows with Xampp.
@lhl this time I did exactly like you have done that too in Amazon EC2 with Ubuntu 18.04. There were no errors but when I go to the public IP it doesn’t show or load anything. This is the message in the terminal. Something is going weirdly off. I too uploaded the writefreely folder into the home folder so the path is
On ec2 be sure to open the appropriate port(s) in your firewall.
If using nginx probably 80 and 443. If just writefreely looks like it needs 8080 open according to your screenshot.
Well, in my EC2 instance there is an inbound rule which allows all traffic through all ports. So I don’t think the problem lies there.
Not sure if you are up and running yet…? But I spent some time this afternoon rewriting the Install process.
It is based on AWS EC2, Ubuntu 18.04LTS, Nginx and a Single User, SQLite Production WriteFreely blog.
I had no problems with set-up, install/config and have a running blog.
Can anyone give a apache reverse proxy config?
Check out writefreely.org. The whole process is there especially the reverse proxy part. Now, if you want even more specifics then you have to check the docs of your Hosting Provider
@lhl I just thought that instead of using reverse proxy, can’t I use standalone? Any issues with that production build? Please let me know.
There’s an example for nginx which I don’t use (and don’t understand fully). Is there the same example for Apache anywhere?