[_lmars]

Really sorry to hear you have had issues with your Flynn cluster. Stability is our number one concern and we are pushing stability fixes all the time.

Flynn does self-heal after node reboots, so if that is not working for you then it is a bug we need to fix.

When you do have issues it would be really helpful to us and other users if you could open a GitHub issue or come and chat to us in IRC (#flynn on Freenode) so we can fix any bugs you are encountering. I fully understand you just want to be concentrating on building your product, this is why we are building Flynn!

[corobo]

Aye like I say I'll grab the logs next time, unfortunately it's happened at the worst possible times so far (e.g. preparing to demo the site so can't really be trying to debug a broken cluster!) so I've not had the time to debug things as they've happened yet. If nothing else I can't fault the installer, it's damned easy to whip up a fresh Flynn!

One of those things where I wish I could say it's something I'm doing that's breaking it but in each of the situations I've had I've not been interacting with it at all when it happens. I know my waffling here doesn't help anyone without logs of some sort, this post just caught me a couple of days after a cluster brick.

I'll set it all up again and will grab the debug info and jump on IRC this time if it all goes to pot.

[jpgvm]

Please do, the node reboot logic has been through a lot of incremental fixes over time and we are always working hard to iron out the wrinkles that are left.

If you don't have time to interactively debug with us on IRC just open a Github issue with what details you can and the output of the `flynn-host collect-debug-info` command and hopefully we will be able to discern what went wrong.

Thanks for trying out Flynn!

[corobo]

I've scribbled the command down and will do so, thanks!

Just to blow away some of my grump cobwebs I'm not just trying out Flynn, I'm still using Flynn! The hiccups were just going to be temporarily patched by hijacking my ServerPilot controlled machine (WordPress on Flynn.. Haven't managed that one yet!) until it felt a bit more stable in the dev/stage environment. :)

[jpgvm]

Awesome!

Would be cool to learn how you are approaching Wordpress on Flynn. I have poked around at writing an asset backend that talks to Flynn's blobstore because a family member wanted me to host their Wordpress site but haven't quite gotten around to it.

We merged the MariaDB database appliance a little while back which took care of the other major roadblock to getting Wordpress to "just work" on Flynn.

I'm `jpg@freenode and josephglanville on Github, hope to see you around. :)

[corobo]

That one was more a "I wonder if I can.." than a required thing so I didn't fully give it a go. I was giving Bedrock[1] a try for it which may have complicated matters further trying essentially to learn two new things at once.

I imagine my thought process at the time was "Flynn is like Heroku and Heroku is all about 12 factor apps. Bedrock seems to be a 12 factor WordPress, I'll try that!". It also somewhat matched up with the rest of what I do in Laravel so the standard composer, PHP, .env, MariaDB vibe. I'll give it another shot over the weekend, I don't recall what stopped it working.

Major thanks on adding MariaDB support by the way, I know mysql and the likes get their fair share of flak but it's what I've used for the past decade or so, more comfortable with it than postgres :)

[1] https://github.com/roots/bedrock