eff it ~ GO LIVE!

BurlesonBrad

Ok, I'm about to get in a fight with my Windows 10 computers and all these dependencies. So, I say "SCREW IT!"

Does anyone want to spin this up on a URL for me? I'm not really looking for a forum for any of my WooCommerce hooplah. I've just been following Flarum's development for a while and I'd like to offer up a collaborative option.

I own viralthreads.com and I've just been simply sitting on it wondering what to do with it.

Stupid domain name right? Well, that's kinda the point!

Call me crazy, but wouldn't this be a great chance to "throw everything" at a Flarum instance and see what happens WITHOUT compromising anyone's actual/real support site, community site, or something you're actually using?

Throw a translation plugin at it, rtl, markdown, logo, custom footer, whatever! Want to add Twitter ~ Go for it! Emojis? Sure! Flags? Why not!

Content? Well, that's where I think we can all pitch in. If we all know that there's a fully working demo running, we can all add comments, share, reshare, tweeder, retweet, post, repost, report, add stupid sh_t, add controversial crap, ...whatever you want!

I'll foot the bill for it :-) And ...I guess we can just start topics and threads about $whatever_the_hell_we_want!!
No really ~ make some stupid politically incorrect or controversial thread about politics, police shooting, mental health, music that you hate, why men have nipples, stupid cat gifs, abortion, alternative energy, global warming, politics (oh wait, I mentioned that one already), gay rights, religion, immigration, gun control, or whatever else.

The point here would be to ALL post something that will generate more content, comment (using whatever account you may or might not want to be a 'real' account) something so stupid that it generates more page views, then share it as often as possible on Fb with a comment about how you agree / disagree on the topic, tweet it to get more views, more comments, and more content. post the link in a Fb group, retweet a comment's URL http://prntscr.com/bfc3qk & do everything and anything imaginable to a fully working Flarum instance!

Then we can all come back over here and discus the error_log, cache issues, php versions (...like php7!), different db options, and whatever else we want to talk over. The point here again, is to totally test the crap outta Flarum!

Thoughts?

jordanjay29

I think most of this is accomplished by our devflarum site hosted by kulga.

Dominion

Or you could help test the official Flarum hosting service while you're at it.

BurlesonBrad

Sounds great Dominion !

Well, poo. You're "all filled up" for the week. http://prntscr.com/bflm11

Perhaps that form should keep accepting entries with a notification about the order of entries and quantity of accounts that can be spun up per week....?

Dominion

BurlesonBrad Perhaps that form should keep accepting entries with a notification about the order of entries and quantity of accounts that can be spun up per week....?

That's certainly something for @Toby and @webeindustry to think about.

webeindustry

Dominion

I've been doing this on more of a feel than strict numbers. There's a few things to take into consideration. I'm okay with the server load as it is now, but as communities mature they take up more resources. The flip side to this is actual support hours spent per week, vs the main goal of offering beta hosting. It's meant to give people an easy means of previewing the software and development of our hosting solution, but overall is a bit of a testing ground for us to gather information and try out some things to be worked into production. If the support hours pile up, that takes away from reaching the launch on time. So it's a balancing act.

For the first week, we had 30 submissions in about 50hrs. I took that as a cue to only open up the form over the weekend, and the last couple I didn't even bother for it. We're sitting around 75 or so instances installed on the server, and while we have a ton of resources free, that could shift if people start heavily using a good chunk of the instances.

I think what might be best is to drop forums not modified within the last 14 days, and keep allowing at a rate of 7-10 per week until launch. @Toby What do you think about that? I think it might be a good idea to add this to the announcement thread. @BurlesonBrad I'm going to open up the registration form for a 24hr window. We'll be glad to get your forum setup.

Toby

webeindustry I think what might be best is to drop forums not modified within the last 14 days, and keep allowing at a rate of 7-10 per week until launch. @Toby What do you think about that?

Sounds good. Let's make that 30 days instead of 14 days though, just to give people some extra leeway. I'll update the announcement post.

Davis

HelpLeecher Maybe you should tone it down a bit. He has good intentions; there's no need to be rude about it.

Kulga

BurlesonBrad wouldn't this be a great chance to "throw everything" at a Flarum instance and see what happens WITHOUT compromising anyone's actual/real support site, community site, or something you're actually using?
...
The point here again, is to totally test the crap outta Flarum!

Exactly why devflarum was created ?
For that niche of testing that can break the forum, requiring database or terminal level intervention (or any level of fixing), please use devflarum. I always give a ? to those who manage to reproducibly break it.

Nearly all extensions / locales are installed as well, permitting users to reliably test all sorts of configurations.
It also sits at dev-master, with specific details of current software version and next upgrade check, so if a bug has been fixed and commited there, it's been fixed.

make some stupid politically incorrect or controversial thread about politics, police shooting, mental health, music that you hate, why men have nipples, stupid cat gifs ...

That I'm sure will work fine with the hosting service. ? You are of course permitted to discuss anything on devflarum, but all changes are reverted after a period of inactivity (and thus ready for the next set of users to try and break)