Flarum Flockport Container

syntactile

Toby That was the ticket. Good catch.

(raul I think the container's behaving just fine in light of the issue Toby referenced!)

crimsonred36

raul How would I go about running flarum in a container on my homelab VM server? The container subnet (10.0.1.0/24) is not routable from my ISP router, but I have forwarded port 80 to my VM (in the 10.0.0.0/24 network) which is running the container. So when I hit my public IP, the traffic is getting translated to the VM IP. I added an iptables NAT rule on the VM for the destination VM-IP to get translate to the container IP, and I added the VM IP in the hosts file and mapped it to the forum URL I'm using.

I can get the nginx page now, but can't understand how to get the forum page.

Edit: I updated the server_name line nginx file at /etc/nginx/sites-available/flarum with the URL for my forum, and now I get a page where the only thing is a link to myflarum.org. Sorry I'm a bit new to nginx/web hosting.

raul

@crimsonred36 would the below be right?

Homelab --> VM --> Container

This is a nested network. Is your VM IP accessible from the host on which you are browsing from?

First thing is to port forward VM IP 80 to Container IP 80. I think since you are getting the Nginx page you have done this.
Second thing is to edit the /etc/hosts file of your browser machine. Associate the VM IP with the Flarum container URL here.

At this point entering myflarum.org should get you to the flarum page.

valgrid

Would it be possible to include slanger in the container? See this post (and discussion).

raul

@valgrid I have to learn more about slanger but at the outset it a ruby app. We already have a Ruby Stack Container available for download, so it should be pretty quick to install Slanger in it, and then have Flarum consume it over the network or a socket.

This way we will have 2 containers, one Flarum and one Slanger. We could also have it all in one container but given the size of Ruby containers - Discourse is our largest container at 350MB, better to keep it separate.

We will try to get this going and update the thread. Anyone else familiar with Ruby and Slanger please give this a shot.

valgrid

@raul there was another suggestion in the thread. Called Ipe, it is written in Go and easily compiled, after that you only have one 7MB binary and one ~450Byte sized config file, so it would be much easier to package and configure (with only one container).

I don't know how this server performs, but it seems to be a better solution for a simple and lightweight Flarum container.

Thank you for your packaging work!

raul

We have just updated the Flarum Flockport Containers to the beta2

Dominion

raul That's great news! I know both @Toby and @Franz are happy to see Flockport supporting Flarum.

I would like to move this over to our "Advertising" tag in keeping with the policy on third-party service promotion that the staff have finally gotten around to formulating. (So many things to do, so little time!) The main purpose of this change of residence is to keep the "Support" tag reserved for issues that users may encounter when installing the software on their own.

Thanks for your understanding and your continued support!

raul

I can understand where this is coming from but I think the advertising tag may be a bit misleading as we do not offer any commercial services or advertising. We are trying to make apps more accessible in this case Flarum itself hence the post here in the hope it could be useful to users, similar to posting a how to guide or tutorial. This also lets our users discover apps like Flarum and try them more easily without the need to install or configure multiple individual components.

Now if we charged users, or had advertising or a related paid service it would be appropriate for instance a hosting provider that offers Flarum. A tag like 'resources' would perhaps be more appropriate. But that's just my 2 cents, so readers know there is no commercial services or advertising on Flockport.

crimsonred36

raul

Hi raul. I have my site up and running now, but I have to get phpmyadmin installed. I followed the instructions here (http://wiki.alpinelinux.org/wiki/PhpMyAdmin), not doing the lighttpd parts since nginx is already on there. I also replaced the symlink to be /var/www/flarum/phpmyadmin. Now all I get when I load the mysite.com/phpmyadmin is a blank page.

I checked the error logs and I see this:

[crit] 995#0: *88 open() "/var/lib/nginx/tmp/fastcgi/0/01/0000000010" failed (13: Permission denied) while reading upstream

Any clues? I tried changing the owner of the /var/lib/nginx/tmp folder to www-data but that didn't help. Tried changing the owner of /usr/share/webapps/phpmyadmin/ to www-data as well, but that didn't work too.

Edit: Solved it. Changed the owned of /var/lib/nginx to www-data as well.

Dominion

raul Thanks for the feedback! You raised a valid point, and it seems that @Toby liked your suggestion of "Resources" for the tag name. We may end up further subdividing the tag as we get more threads added, but for now, "Resources" it is!

This site, like the software itself, is still a work in progress. So if you have any more ideas on how we can make things better, feel free to start a thread with the "Meta" tag and let us know!

raul

crimsonred36 - great you figured it out!

Some Flockport PHP containers already have phpmyadmin, adminer and opcache. It's documented in the Flockport Guide. The Flarum container has all 3, and the microflarum container has adminer.

These are located in the '/var/www/shared' folder. If you have a look at the Nginx config in '/etc/nginx/common/locations.conf' you will see how it is accessed.

It's available at 'myflarum.org/fp/' or 'containerIP/fp' location and protected by basic http-auth and the default user and password is flockport. If you browse to the /etc/nginx/sites-available/flarum' file you will see an include line at the bottom that references the locations.conf file. If you comment this out this access is disabled.

Since you are using the microflarum container it has adminer in the '/var/www/shared' folder. If you prefer phpmyadmin just download and place it in the '/var/www/shared folder'. Now you can access it by pointing you browser at 'myflarum.org/fp/'.

You can change the httpauth password by using any htpasswd utility, in Alpine Linux the apache2-utils package has the htpasswd utility. The password is stored in the '/etc/nginx/htpasswd' file. In Debian containers we usually include a 'crypt.pl' perl utility in the /var/www/shared/folder that can be used to change the htpasswd file credentials.

You can disable this access by deleting the '/var/www/shared' folder or deleting the related config section in '/etc/nginx/common/locations.conf'. It's a good idea to simple rename the /var/www/shared folder when you don't need to access the utilities so there is no access.

« Previous Page