homepage design for poddery.com

Yes, lets move it live and continue working. I would prefer to use Free Software instead of Open Source as the 3 main points though.

Also we can keep savepoddery.com content as save.poddery.com so we don't have to spend on one more domain for long.

Have discussed regarding savepoddery with Anish. Let that be with github, so that we just need to update the dns.

or if that doesn't cost us too much, we can keep that running.

@balasankarchelamat @nandajavarma @jishnu @hrishikeshakastult And others, please state your position

Lots of links would be broken and it is a historic domain we can always refer people to (not just the data, but preserve as it was).

@praveenarimbrathod Consider that, with cost of domain, I can print about 1400 Black and white leaflets for diaspora promotion.

Perhaps make some changes and convert it into donate.poddery.com so people can regularly contribute to the maintenance?

@vamseekanakala That's great.

The trial period Knightswarm offered is ending by this month. An invoice of $486 for 3 years has been generated in the Client Area. Those who are in charge of the financials, do the needful to make the payment on time.

There wasn't any issues with the pod after the migration. So, I hope everyone is fine with having Knightswarm as the hosting provider for poddery.

Just updating, we have made the payment for hosting poddery.com for next 3 years. Next is transferring ssl certificate. I have created another thread for it.

I'm renewing the domain for at least one more year since the main concern was the cost, I'm paying for it from my pocket. Those who want to move it to save.poddery.com or donate.poddery.com can setup a redirect when it is ready. I hope @anisha will print 1400 pamphlets too.

@praveenarimbrathod I would suggest the other way. Move all files to save/donate.poddery.com and point savepoddery.com to the new address. In that case, all links will stay intact and the search engines will start indexing the new ones. Also, once savepoddery.com expires, nothing more needs to be done from the admin point of view.

How about we move save.poddery.com to gitlab pages?

https://github.com/savepoddery/poddery.com/issues/1

@manukrishnantv @anisha @fayadfami @balasankarchelamat @vamsee @niteshajain @nandajavarma

Can we wait till we configure git.fosscommunity.in? Putting everything under GitLab is again making things centralized.

I have no issues moving it to GitLab if most of the members are in favor of.

We can't use git.fosscommunity.in for this thing, as Gitlab Pages is only available in Gitlab EE, not Gitlab CE which we are planning for git.fosscommunity.in

@balasankarchelamat @manukrishnantv how about we add a site in poddery.com nginx? Since its a low volum site, it won't impact poddery.com bandwidth Also since nginx is already loaded, impact on RAM usage won't be much.

Or even better, how about adding it as poddery.com/save and redirecting save.poddery.com there?

@manukrishnantv the main issue with github is not centralization, but proprietary software. Since git itself is centralized, everyone has a copy of the whole history, so even if github.com shuts down we are safe.

Running a static site within poddery server is of negligible load. I'd choose to go with that and use gitlab for version control.

Since we have our gitlab instance, I moved the repos to to https://git.fosscommunity.in/community/poddery.com and https://git.fosscommunity.in/community/save.poddery.com

Glad to be on our own and not having to depend a proprietary service.

save.poddery.com is now served from our new scaleway.com server.