@RemahI didn’t say development - I said “staging/testing”. I’m talking about a staging environment to test things such as an importation of messages from another platform, etc.
No, I am not spamming the forum. This is a different thought process altogether. What you mention is regarding a backup problems or flaw that exists in the system and the standard “backup/restore” path that some might consider as an option to this path, however it is not the only path to follow and therefore I’m exploring another option of setting up such a staging environment presently by going down an altogether different path.
My comment was pointed: I said “developer” because you have “developed” a non-standard Discourse install.
We know that such configurations generate a lot of issues that are not relevant to the majority of instances using the officially supported install method.
I referred to the topic you created because it is a case in point.
Remember this topic. It is not a discussion of variations from the norm but a request for standard steps:
Your instance is a long way from such standard set of steps:
This topic becomes muddied the more unsupported configurations that are included here. The official install has a population of hundreds or thousands where advice will generally be applicable to all. Whereas non-standard installs often have a population/sample size of one so it is far better to put them in separate topics because some advice will be misleading for the majority.
I’m not trying to dissuade you from posting what is likely to be very useful information for some sites. Your contribution will be more useful and more easily referenced with its own title in its own topic.
$ git status
# Na branch master
nada para confirmar, diretório de trabalho limpo
$ git fsck
Verificando diretórios de objetos: 100% (256/256), concluído.
Verificando objetos: 100% (5038/5038), concluído.
Quero preparar a atualização para a versão 2.7.0.beta2, mas isso parece estar impedindo que eu comece no mesmo ponto dos servidores de produção
