Iniciar una nueva comunidad de Discourse con base de datos antigua

Hola a todos, buen día.

Es posible que hayan sabido que creé mi primera comunidad de Discourse hace más de dos semanas en AWS, pero utilicé su imagen AMI de Bitnami, que, por supuesto, no es la instalación compatible. Y como era de esperar, tuve problemas e intenté hacer todo lo posible por resolverlos, pero seguían acumulándose. El último problema que tuve fue un error 500 (error del servidor) que impedía mostrar mi comunidad. Tuve que reiniciar mi servidor y, como un relámpago, perdí todo lo que había construido en las primeras dos semanas. ¡Eso es mucho contenido, créanme!

Aunque no voy a llorar por la leche derramada (obviamente, esta comunidad tiene suficientes advertencias sobre el uso de los detalles de instalación recomendados, que es lo que haría mi persona arrepentida ahora :grinning:), no quiero empezar desde cero nuevamente con la base de datos y el contenido. En resumen, estaría encantado si alguien pudiera ayudarme con información concreta sobre cómo obtener los detalles de la base de datos y toda la información necesaria que se integraría en mi nueva instalación, para que aún pueda tener todos los registros y detalles de los usuarios registrados y sus actividades. De esta manera, nada se habría perdido realmente en todo el proceso. Sería una curva de aprendizaje para mí.

Y un punto importante a tener en cuenta: seguiré alojando en AWS. Al menos, hay un proceso de instalación recomendado que involucra Docker, y además, mis 1.000 dólares de crédito no pueden desperdiciarse. Por lo tanto, estaría encantado si toda la información estuviera adaptada para su uso en su plataforma con cualquiera de sus servicios que hagan que este maravilloso viaje valga la pena.

Y no lo griten: mi comunidad en crecimiento está fuera de línea desde hace 3 días. Así que tengo que salvar mi reputación. ¡Vamos a hacerlo, gente!

2 Me gusta

If you have a discourse backup file, then you can restore it to a new server fairly easily. Do you have a backup file?

1 me gusta

No, I don’t. Barely added or configured anything. But is there still a way possible?

I am not familiar with the Bitnami image, so I can’t say for sure. Do you still have access to the Postgres database in some way?

3 Me gusta

No, I don’t too. But I can get access to it or find my way around it. And besides, I think I took a screenshot when I initially installed the software but not later. So can any of this?

  • Backup old site, download backup
  • bring up new site
  • Restore from backup
  • ???
  • ???
  • PROFIT11111!!!

If this isn’t possible, don’t use unsupported install methods.

Hello @robbyoconnor, I think I understand your point to the third one but got lost with the multiple ??? And Profit 11111… If you don’t mind, can you be more specific? I’ll appreciate.

Safe to ignore everything after #3

1 me gusta

My recommendation here would be to restart your community from scratch with a supported install and ensure you enable automatic backups to s3 this time

I appreciate that losing two weeks is not fun, but given you are struggling to get access to your data… there is not much we can do

2 Me gusta

Hi Sam, thanks for your candid reply. I think I might just do that and throw some apologies in the air to the people who started with me for the fun 2 weeks we had. Besides, Discourse has been fun, though.

Yeah, nice opinion. But think I’d be taking @Sam 's opinion. That’d be ‘too long’ a try for something that may not work. So starting a new one from scratch would be better. Just wish I had stared earlier than wasting half a week hoping to hold enough water in a basket.

Went through the supported installation details for AWS, but unfortunately, it’s not the official documen from the Discourse Team. And then surfed through the web and was able to come up with this that gives detailed instruction about installing Discourse on AWS using supported instances from Discourse. So just for the asking and staying on the safer side, is this install method going to give me the supported Discourse software? I’d love to hear your opinion, @Sam?

I’m not sure if you have actually looked at the official Discourse install guide which is the only supported install method I’ve heard of.

Other users have referred you to it in your other topic, e.g. this reply:
https://meta.discourse.org/t/can-not-configure-my-bitnami-discourse-instance-to-send-out-mails/101618/2?u=remah

You will see on other topics that AWS/Bitnami installs are not supported although people may still be able to help you, e.g. as in this topic:

https://meta.discourse.org/t/just-installed-discourse-on-aws/86146?u=remah

FYI, here is some background on the AWS install guide that you found.

The blog owner is a user here, @stroupaloop, although I haven’t seen him posting for a while.
He had a couple of topics on AWS that I read when i first joined:

Wow, thanks a bunch for this Remah. I actually saw an installation guide here on Meta about installing on Amazon; not with Bitnami, but from scratch. So whilst I wouldn’t call that the official install guide, I believe the installation process still installs Discourse the normal way it was meant to be installed-with Docker. The installation guide is here on Meta, and will link to it once I’m done with this post. (I’m on mobile)
Edit: This is the install guide I was referring to.
So a quick one:
What do you think?

  1. Install a new community using the guide I now shared its link or
  2. Starting a New Digital Ocean droplet.
    And note: I have over $1k in my Amazon credit. The only reason I’d paid for that is because of Discourse hosting for about two or three years, depending on the resources I use.
    But paraphrasing the question properly, I’d ask: If I install using the guide by @Frez, is it going to come with support here on Meta if I run into trouble? Believe me, I’d prefer to get help here than from any other place; including Bitnami, which I have now ditched. Better to source for help from the source!

Thank you for your time. I appreciate!

1 me gusta

Yes, David, I have access to the postgres database.

I can’t say what will get support. You’ll have to get that from the Discourse team when they’re back in the day time.

While you wait for a reply from the Discourse team, then why not try out option 1. If everything installs fine then you can check that it works perfectly before going public. Option 2 would be your fallback if option 1 doesn’t work OK and you cannot resolve the issues.

One caveat is that the guide is over two years old - last edited April 2016. Since then there has been at least one problem identified. This problem with SES email was resolved but I don’t know if other problems are out there:

2 Me gusta

Thanks again Remah for your input. You’ve done me a whole lot of good, you know? Glad to have you here.

The only setup we support is this one: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub

Typically people do that on a digital ocean droplet, but it should work the same on any linux server.

The problem with AWS is the complexity - finding the right way to set things up is very tricky. Is your AWS credit valid for AWS Lightsail? That provides a ‘Digital-ocean-like’ experience on AWS: Virtual Private Server and Web Hosting–Amazon Lightsail—Amazon Web Services

There is no requirement to use SES, you can use another recommended provider, even if your server is hosted on AWS.

3 Me gusta

The guide @habeycole referred to assumes that SES is used. Another reason why that guide needs an update.

2 Me gusta

Yes, my credit is eligible to work with Lightsail. Think it’d be better using that then. But think I’ll also do EC2 install and check for which works best for me in the next two days before I eventually settle for the better. I appreciate the feedback I’ve received from all.

And to note: I possibly won’t be using SES for sending mails because of the restrictions. Mailgun is my preferred choice.