Vocês podem ter ficado sabendo que criei minha primeira comunidade Discourse há mais de duas semanas na AWS, usando a imagem AMI da Bitnami, que, claro, não é a instalação suportada. Como esperado, enfrentei problemas e fiz o meu melhor para resolvê-los, mas eles só foram se acumulando. O último problema foi um erro 500 (erro do servidor) que impedia a exibição da minha comunidade. Tive que reiniciar o servidor e, num piscar de olhos, perdi tudo o que construí nas duas semanas anteriores. É muita coisa, acreditem!
Não estou chorando por leite derramado (obviamente, essa comunidade já tem avisos suficientes sobre usar os detalhes de instalação recomendados, e é isso que minha versão arrependida fará agora ), mas não quero começar do zero novamente com o banco de dados e o conteúdo. Resumindo, ficaria muito grato se alguém pudesse me ajudar com informações concretas sobre como obter os detalhes do banco de dados e todas as informações necessárias para integrá-las à minha nova instalação, de modo que eu ainda possa manter todos os registros e detalhes dos usuários cadastrados e suas atividades. Assim, nada de verdadeiramente importante teria sido perdido no processo. Seria uma ótima oportunidade de aprendizado para mim.
E um ponto importante a notar: continuarei hospedando na AWS. Pelo menos, há um processo de instalação recomendado que envolve Docker, além disso, meu crédito de US$ 1.000 não pode ser desperdiçado. Portanto, ficaria muito grato se todas as informações fossem adaptadas para uso na plataforma deles, com qualquer um dos serviços que tornem essa jornada maravilhosa valiosa.
E não espalhem isso: minha comunidade em crescimento está offline há três dias. Tenho uma reputação para salvar. Vamos fazer isso, pessoal!
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?
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.
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
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?
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?
Install a new community using the guide I now shared its link or
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!
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:
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.
), mas não quero começar do zero novamente com o banco de dados e o conteúdo. Resumindo, ficaria muito grato se alguém pudesse me ajudar com informações concretas sobre como obter os detalhes do banco de dados e todas as informações necessárias para integrá-las à minha nova instalação, de modo que eu ainda possa manter todos os registros e detalhes dos usuários cadastrados e suas atividades. Assim, nada de verdadeiramente importante teria sido perdido no processo. Seria uma ótima oportunidade de aprendizado para mim.