If you know some SQL, you can navigate around the database . show tables and then select * from <tablename> , show create table <tablename> are some commands to know. But these things are very specific to each app and each app's database keeps changing for every release. It would be hard to track these changes via docs.

@ramiroro what is false meant to be in this context? I tried understanding the docs but didn't understand. Does it mean those files are not downloaded anymore? How does the portal work then without it? I am not even sure why it downloads from 3rd party sources. I guess they are using it to get some analytics of selfhosted installs?

@ghstandard putting an ads.txt at top level works for me. [image: f7dfcf9b-6ec3-4b53-8180-e52e12172ffc-image.png] Then, if I go to https://blog.domain.com/ads.txt , I can see the file. Are you able to navigate to the URL and see the file ? If so , maybe this is some caching issue on Google side.

Made a new mailgun account and it works fine now. I was grandfathered in on the old mailgun that was free, but apparently they won't let you send in bulk...

hm actually the latest published package version is 4.52.3 with upstream version 5.52.3 (for ghost those two versions are a bit confusing sometimes) can you check in the app eventlog which versions were applied and from which version it was coming?

Since the latest update it no longer fails. It doesn't do what I want (embed the calendar in a page) but that's Ghost's problem, not Cloudrons. https://inner.transitionmovement.org/calendar/

If you like, you can also test on https://my.demo.cloudron.io (username/password: cloudron).

@Sam_uk seems to have extensive code changes and also how the app is built. I fear this will not be maintainable in the long run. Do you know why the upstream project does not just rely on local assets?

Good suggestions, made the changes.

@jdaviescoates thanks, that makes sense. I have added it.

I don't actually think any php code will be run within the Ghost app, unless Ghost itself would call the php interpreter. Ghost is a nodejs application.

@girish Yes I did. I bumped the memory limit to 4096, in the ENV file and in the Cloudron admin panel for the app.. I upgraded my linode to 8GB of Ram too, just for this. Solution: increase both poste & my SQL database memory limit in Cloudron services tab, to 2GB each. Reverted back to default after import I then restarted the entire server, and began the process of importing. it then worked! @girish May I suggest to include the solution in the documentation for importing. This was a fairly large import with nearly 4K posts. How do I flag this as solved?

@nj thanks, I have pushed the update.

@robi, very cool. Usually, when I spend enough time getting familiar with the applications, I find that the Cloudron team has already dialed it in. Will keep this in mind

@girish So, after updating for recent versions, my main.yaml file looks like this: name: Deploy Theme on: push: branches: - master - main jobs: deploy: runs-on: ubuntu-20.04 steps: - uses: actions/checkout@v3.0.2 - uses: TryGhost/action-deploy-theme@v1.6.1 with: api-url: ${{ secrets.GHOST_ADMIN_API_URL }} api-key: ${{ secrets.GHOST_ADMIN_API_KEY }} I've also renamed the Github repository to: Basho-master--34- so that it matched the theme name on Ghost admin: basho (Basho-master--34-) Version 2.3.0 On every commit, the "deploy" action is triggered. There is an extensive log, where the only issue is the "canary" version parameter copied above. Otherwise it announces a successful upload, but my theme files are not updated. I'm not sure where the repo gets uploaded, I guess...

@jdaviescoates good idea! Seems it would require some hacking to get working in Ghost, a good suggestion for the upstream devs. The API seems mostly undocumented, hence would be useful to know if they followed a particular pattern of another API mail provider.

@kris X-Forward-For header is already set, can you use that instead?

@fbartels Thanks, guessed as much. Something we'll need to have a think about.

@jdaviescoates Oh, it was made available to all only yesterday. So, probably takes a couple more days to actually auto-update.