nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Where are the app-link configurations found at a file level?

admin admin_trokdm

I have Atlassian Jira and Confluence Docker server which are redelivered monthly with updated containers.

The home directory is retained through iterations, but I have recognized that the app-links need to be recreated on each iteration; So I speculate they are not retained in the home directory. They are also not found in volatile memory, as they are retained during an on/of cycle, so I speculate that they are retained in the installation directory?

In any case I need to retain these files to automate this and reduce my Docker server maintenance period after upgrades, and am looking for where they are located on Jira and Confluence servers.

Accepted answers

All comments

Nic Brough -Adaptavist-

They are not. Application links are held in the database.

Peter DeWitt

@admin admin , Like Nic said, they are stored in the DB. Check this page out for a bit more information.

https://confluence.atlassian.com/jirakb/how-to-remove-application-link-directly-through-jira-database-285839519.html

They have some example of querying the link key and deleting if necessary. I'm not confident there is a good way to create. Maybe if you run a DB export / Import for those specific objects? But that could go very badly...

admin admin_trokdm

Yea, I agree with you that doesn't seem wise; Though admittedly I am in a validation environment, and that is what I developed it for =-)

I am looking for a consistent method I can create app-links to my known servers rapidly via automatable means.

admin admin_trokdm

I need a scripted approach to add app-links to already known/created applications, which already have application links created to the server;
I'm developing this for Docker containers I've delivered in the past for Atlassian Jira and Confluence.

My team has become frustrated with our ability to rapidly upgrade; As the application links are not replicated into the new servers, and require manual administrative installation;

This is why I was unclear where the app links are maintained, because I am using an external database, and the app links are not retained through upgrades to the container.

It seems muddled to me where this configuration is actually maintained, because if it is only in the db, then it would be duplicated successfully into our upgrades.

Nic Brough -Adaptavist-

You say that the application links are not replicated - could you explain what you are doing that removes them? When I copy Atlassian systems across servers, things like application links are kept, so I'm wondering what you're doing to lose them.

admin admin_trokdm

They are not removed per-say, but they are unusable, requiring removal and re-installation.

Business needs have changed drastically from when I first began administering Atlassian software; Initially we were handling the servers ad-hoc, but this became frustrating for our developers who required upgrades more frequently; So I planned, designed and delivered Atlassian containers mid 2016 to provide a far more flexible infrastructure.

This change went well, but we then delivered these containers behind a reverse proxy with https, which threw a wrench into the whole affair.

admin admin_trokdm

As far as app-links are concerned that is.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server