Moving to Github

Going forward all public infrastructure things related to FEO will exist in this repo

If you would like to audit/make PRs/open issues and generally contribute to the health of this community in a more technical way, this is your place to do it. I know we have a lot of technical people that have brought up wanting to contribute, so I want to provide a reasonable platform for doing this.

I am trying to keep as much of the devops/sysadmin stuff in Ruby as possible as it seems there are a lot of Ruby developers, so maybe we can capitalize on that.

over time I will add known contributors to the organization if they desire and hopefully we will achieve a critical mass of contributors to have some sort of federated approach to improving the technical aspects of this community.

Next Steps

1. Forking the current theme & adding it to this repo
2. Adding plugin recreation to Docker builds so admins don't have to go through a bunch of headache with every upgrade
3. Add my cron entry scripts to the monorepo that handle backups
4. Actually work on the theme to improve accessibility and other issues
5. sanitize and publish the config.json file that controls FEO so quickstart is a bit easier

Other Resources

1. FEO Docker Image
2. Docker Compose quickstart

Node. Redis. Docker. What is this the hipster fan club?

For the record: I love both Redis and Docker. I think Node is a steaming pile of shit that I'm forced to use on a daily basis. That is all.

P.S. Open Source stuff rocks so hooray for opening up your configs and files.

@spiffyjr said in Github Repository:

Node. Redis. Docker. What is this the hipster fan club?

For the record: I love both Redis and Docker. I think Node is a steaming pile of shit that I'm forced to use on a daily basis. That is all.

P.S. Open Source stuff rocks so hooray for opening up your configs and files.

Node makes my life so much easier on a day-to-day basis, but then I'm playing massive amounts of catch up going from two-three web design classes to having coded entire sites in less than six months. NPM, laravel elixir and github have made worlds of difference!

Ditto on the P.S.

Laravel?! Kill me please. A Framework for Web Artisans. More like a Framework for Assholes (Taylor, the author, being that asshole).

@spiffyjr said in Github Repository:

Laravel?! Kill me please. A Framework for Web Artisans. More like a Framework for Assholes (Taylor, the author, being that asshole).

ROFL. I'm given two options at my company. Wordpress and Laravel. I just finished a site in wordpress and while it's 100000x more end-user friendly, the backend was a clusterfuck of epic proportions and took almost twice the amount of time.

With Laravel, it felt like I went straight from Point A to Point B in while creating customizable components. With Wordpress I was getting to Point B from Point A via Point X-Y-Z.

What kind of frameworks do you prefer to build in?

Phoenix if I have my druthers, Express is usually when I don't.

Phoenix looks really interesting. Unfortunately, where I'm at now they want every website to be Wordpress so instead of charging my web dev per hour charge for updating the content on a page, they can have the digital coordinator do it at half the cost.

I might play with Phoenix on some personal projects though, thank you!

Anything that's not Node. Seriously, how the hell did a language with such a shitty concurrency model ever become mainstream.

Anyway, I develop all my sites using Go for the backend API and Angular for the front-end. If it's required I'll run express to render the site server-side and transition to a single page app. Usually this isn't the case so it's just nginx serving static files and all the data comes from an API.

I have a super simple Go API running on a 0.5 core / 1 GB memory box on Google Cloud that's handling 10 to 40 million requests a day. This is one of the many reasons why Go is amazing and I urge anyone wanting to be serious about web development and performance to at least look at it.

@spiffyjr Thanks for that, I'll look into it. I'm bound to whatever my backend developer chooses to work with (when he's not forced to work with Wordpress), but I can always make suggestions. I do prefer nginx over apache, hand over fist.... we're recently started swapping all of our local dev to it, regardless of framework.

That said, I think Node is not the best system to build a massive server web. I would definitely use Go for that. And honestly, that's basically the reason why I left Node. It was the realization that: oh, actually, this is not the best server side system ever.

That's a quote from the Node founder who quit the project and is now working at Google in one of their fancy schmancy brain thingies.

And the article if you're curious.

I appreciate your passion for Go, but Go has several problems itself, i'm not sure it's useful to arbitrarily crap on a language to anyone that is still developing their ideas about development.

Node's concurrency model is not awful, it just requires understanding of Futures and other asynchronous concepts instead of them being abstracted away by some runtime scheduler. If i was to assign arbitrary comparisons between the two languages, I would say that the greatest advantage of Go is strong types, however writing even simple error handling in Go is absolutely awful compared to many other languages (in my opinion Elixir has the best error handling model possible)

All in all, there are lots of tradeoffs between languages, Go is very good at what it does (and generally I personally also like a language that has compile time guarantees), but it's also sometimes really annoying when prototyping.

*I do not write Go on the day-to-day, I really only do it for experimental side projects.

What good is it to be a developer if you can't force your dislike of languages on other developers?!

I hate everything equally. That being said, I hold a special level of hatred in my heart for developing wordpress templates.

Oh look, I think I can still see the thread topic over there, on the horizon!

Quiet you. Somebody said Wordpress. I heard it from afar. WORDPRESS IS AWFUL. How dare you even speak its name?! It's what web design would look like if all web design were descended from AOL Pagemaker and then it was ported to Mac OS 7.1 then translated into Arabic by someone who only speaks French and then back to English by dogs but instead of translating it the dogs got drunk and spilled a bunch of dog beer on the code and it got all smudged so they hastily tried to rewrite it in QBASIC while they were still pretty buzzed. Then the dogs uploaded it to GoDaddy and said "Who needs php turned on? Look! Danica Patrick! Also try our CMS!"

You heard it here first. Wordpress is a CMS designed by drunken french arabic dogs in QBASIC for Mac OS 7 at the request of America Online. It's a widely believed FACT.

TL;DR - I'm planning to check out what I can fiddle with on Github later tonight. Thanks for putting that up.

I'm working on how to best manage the forks and bringing them into the monorepo but these are the two forks that will be added : nodebb slick theme