<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>confluence on Christian Knedel</title>
    <link>https://www.christian-knedel.de/en/tags/confluence/</link>
    <description>Recent content in confluence on Christian Knedel</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Apr 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.christian-knedel.de/en/tags/confluence/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cool things with Atlassian: Custom macros in Confluence</title>
      <link>https://www.christian-knedel.de/en/post/2021/april/20210418-atlassian-confluence-macro/</link>
      <pubDate>Sun, 18 Apr 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.christian-knedel.de/en/post/2021/april/20210418-atlassian-confluence-macro/</guid>
      <description>Confluence is the gold standard in the knowledge base space. Creating your own Confluence user macros is also a snap. Today I&amp;rsquo;ll show how I created a terminal macro.    Step 1: Create user macro I click on &amp;ldquo;User Macros&amp;rdquo; &amp;gt; &amp;ldquo;Create User Macro&amp;rdquo; in the &amp;ldquo;Administration&amp;rdquo; area.    Then I enter the user macro name and select the &amp;ldquo;Define user macros&amp;rdquo; option &amp;ldquo;Rendered&amp;rdquo;.    Step 2: Develop user macro Every &amp;ldquo;rendered&amp;rdquo; user macro has a body variable by default:</description>
    </item>
    
    <item>
      <title>Uncool with Atlassian: how to deal with Atlassian policy</title>
      <link>https://www.christian-knedel.de/en/post/2021/april/20210414-docker-atlassian-politik/</link>
      <pubDate>Wed, 14 Apr 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.christian-knedel.de/en/post/2021/april/20210414-docker-atlassian-politik/</guid>
      <description>Atlassian has stopped selling the small server licenses and I have been thinking for a long time how to deal with this. Since I still want to use my installation for a long time, I implemented the following measures:
Measure 1: I use Docker exclusively I run all Atlassian tools as Docker containers. Even older, native installations can be converted to a Docker installation via database dumps. These can then be conveniently run on an intel Nuc or a Synology disk station in the Homelab.</description>
    </item>
    
    <item>
      <title>Synology-Nas: Confluence as Wiki System</title>
      <link>https://www.christian-knedel.de/en/post/2020/february/20200213-synology-confluence/</link>
      <pubDate>Thu, 13 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.christian-knedel.de/en/post/2020/february/20200213-synology-confluence/</guid>
      <description>If you want to install Atlassian Confluence on a Synology NAS, then you are in the right place.
Step 1 First, I open the Docker app in the Synology interface and then go to the sub-item &amp;ldquo;Registration&amp;rdquo;. There I search for &amp;ldquo;Confluence&amp;rdquo; and click on the first image &amp;ldquo;Atlassian Confluence&amp;rdquo;.    Step 2 After the image download, the image is available as an image. Docker distinguishes between 2 states, container &amp;ldquo;dynamic state&amp;rdquo; and image/image (fixed state).</description>
    </item>
    
  </channel>
</rss>
