please migrate threads from the community forum that is shutting down

[mailinglists35]

Describe your suggestion as much as you can

for example I find useful articles via google such as https://community.bitnami.com/t/job-for-bitnami-service-failed-because-the-control-process-exited-with-error-code-see-systemctl-status-bitnami-servic/102731/2

but the header of the page says it will be shut down 15 july

[jotamartos]

Hi @mailinglists35,

We migrated the most shared post in our community forum to this new platform. If there is another ticket that you want here, you are free to open an issue here and post the solution you found in the community forum.

Thanks

[tomredsky]

The answers to the questions I had are still in Google index yet when I click on them I am directed here and there is no results for them in closed/open issues That's going to be painfull for all concerned.
Would you like me to post my "How do you change the Wordpress upload directory?" to this Bitnami VMS issues?

[ibushong]

Hi @mailinglists35,

We migrated the most shared post in our community forum to this new platform. If there is another ticket that you want here, you are free to open an issue here and post the solution you found in the community forum.

Thanks

Assuming you are referring to the initial "closed" issues created by @agomezmoron (side note: I thought this was a clever wordplay of "Agamemnon", but seems it's just an unfortunately hilarious (for English speakers) portmanteau of his real name), I see only ~35 of those. There were WAY more posts on the original community forum. Why can't you just make the old community forum read-only, and add a header/alert directing users here if they want to ask something new?

There is so much useful knowledge and discussion contained in that forum. I can't image why you would want to remove that... Additionally, from an SEO perspective, I would imagine you are going to lose a ton of organic traffic, once google discovers that all of that content is gone.

[jotamartos]

Hi @mailinglists35 ,

I see only ~35 of those. There were WAY more posts on the original community forum.

We know. We migrated the most shared posts in our community forum and the ones that resolved most of the issues during the last months

Why can't you just make the old community forum read-only, and add a header/alert directing users here if they want to ask something new?

There is so much useful knowledge and discussion contained in that forum. I can't image why you would want to remove that... Additionally, from an SEO perspective, I would imagine you are going to lose a ton of organic traffic, once google discovers that all of that content is gone.

Keeping the server up and running costs money. We evaluated the pros and cons and decided to keep the info available until July 15th. The server is now stopped.

[tomredsky]

With respect, I think that evaluation process was flawed. While a shared posted are no-doubt a indicator of it's popularity, is it not definitive. Page impressions would have given you a better coverage.

I appreciate servers cost money but I would have thought a read-only version of the forum would have been reasonable affordable. Over time, it would recieve fewer and fewer hits and so the number of instances reduced.

[ibushong]

A read-only version of that site would probably cost ~$100/month at most (especially when using all the optimization techniques I learned from those posts, which are now gone...). And you could easily make that back by slapping AdSense on it.
Also, how much is it going to cost your engineering/CS team to answer the new flood of questions that can no longer be self-answered via google?

[luethralf]

If shutting down community.bitnami.com was intentional, I think this is a bad idea.

Example: I am trying to set up a bitnami redmine server. Until last week I was able to access hundreds of articles with possible solutions to problems. All of these are gone.

This will lead bitnami users to switch to other products.

[recena]

FYI #133 (comment)

[nccerhostmaster]

How thoroughly disappointing.