Replies posted by Leon Kroon

10 Replies

T
Apprentice
techniekwebshopApprentice
asked in Questions & Conversations

Trouble with Docker image

Currently, version 2023.2.12 for both Universal and Indicium are tagged with latest. Our most recent releases are always tagged with `latest`.For as far as I know, there is no simple way to see which version is used with the tag `latest` other than comparing the SHA256 hashes of each image and see which tags match the hash. I would not recommend spending too much time on this, since there is a simpler way.The simplest way to see the version of the tag `latest` is by navigating to the running instances. For example, check the Indicium page which version number it displays.Keep in mind that Docker (and Docker Compose) first require a pull (e.g. docker compose pull and then docker compose up -d) to ensure the tag `latest` still matches the actual latest version available on the remote registry.As for the error(s) in Indicium, these end up in the logfiles, which are located in the directory `/opt/indicium/Logs`. The easiest way to access these logfiles is with a path mapping, for example .

11
Anne Buit
Community Manager
6 months ago
T
Apprentice
techniekwebshopApprentice
asked in Questions & Conversations

Trouble with Docker image

Great to hear you got it working!As for the http code occurring with Indicium, I assume the certificates are applied for both the Universal and Indicium service. Are the used versions for the Metasource, Universal and Indicium the same? According to your previous screenshot, they should all be on version 2023.2.

11
Anne Buit
Community Manager
6 months ago
T
Apprentice
techniekwebshopApprentice
asked in Questions & Conversations

Trouble with Docker image

Hi @techniekwebshop, I have not tested this, but I suspect the path you specify in certFile and keyFile need to exist inside the running Traefik container and not on the host machine. This can be solved with a volume/path mapping for the Traefik service.It also is possible to add the following to the Traefik service for extra logging output:command:      - "--log.level=DEBUG"

11
Anne Buit
Community Manager
6 months ago
T
Apprentice
techniekwebshopApprentice
asked in Questions & Conversations

Trouble with Docker image

Hi @techniekwebshop, the reverse proxy used in the example (and in the configuration you used) only routes traffic coming from the domain localhost to the backend containers, traffic coming from any other source will not get routed. How to route incoming traffic is configured with labels for the Indicium and Universal service called traefik.http.routers.<routername>.rule= .The documentation was updated very recently to add the ability to specify a hostname or IP address through the .env file, this might solve the issue.It is also possible to manually edit the docker-compose.yaml file by replacing the entries at all labels containing localhost with the hostname or IP address to your liking. I also noticed you are running an older version of Indicium against the current metasource version. I would recommend using a newer version of Indicium by changing the used tag.

11
Anne Buit
Community Manager
6 months ago
T
Apprentice
techniekwebshopApprentice
asked in Questions & Conversations

Trouble with Docker image

Hi @techniekwebshop , a few things to try:Are you able to reach Indicium when you add port mapping to the Indicium service in the compose file? This can be achieved by the following example, this will map port 8080 externally to port 80 of the container:ports:     - 8080:80   On what device are you trying to reach the deployed containers, the described setup will only work when accessing it on your own machine.

11
Anne Buit
Community Manager
6 months ago
Freddy
FreddyThinkwise Local Partner Brasil
asked in Questions & Conversations

Indicium connect to Database on another port

​Hi @Freddy, when referring to Localhost, the Indicium container will try to connect with itself on port 1433. Each container you run has its own internal IP address. To connect to a database, you will need to specify the correct hostname or IP address. If these containers are run on Docker, the internal DNS of Docker could be used for this to avoid hardcoded IP addresses (in case of connecting from one container to another).For example, a service defined with the name “container1” in a Docker Compose file can be resolved (and pinged) by all other services with containers defined in this same Docker Compose file, because Docker Compose automatically puts all defined services in the file into the same custom network.The same can be achieved by manually putting all created containers into the same custom Docker network.

2
E
Moderator
1 year ago
L
Moderator
Leon Kroon
published in News & Blogs

Introducing the Thinkwise Container RegistryBlog

​  Hi @Leon Kroon , We've decided to host our own cloud environment and I'm trying to use the container registry. Any idea what can be the issue here?  Successfully logged in, pulled the image.. it says it has read the appsettings.json file..  but it cannot connect.. however if I run dotnet indicium.dll in the shell it connects.   I found it, for some reason, when you run Indicium in a container it cannot access the SQL server via Localhost.. the external IP I also use to connect via SMSS does work.    Hi @Freddy that is correct, when referring to Localhost, the Indicium container will try to connect with itself on port 1433. Each container you run has its own internal IP address. To connect to a database, you will need to specify the correct hostname or IP address. If these containers are run on Docker, the internal DNS of Docker could be used for this to avoid hardcoded IP addresses (in case of connecting from one container to another).For example, a servi

47311
Freddy
1 year ago
L
Moderator
Leon Kroon
published in News & Blogs

Introducing the Thinkwise Container RegistryBlog

Hi @Freddy, if AWS ECR offers image replication, it should be able to work. However, I have not tested this. 

47311
Freddy
1 year ago
H
Vanguard
Henk-Jan van LaarVanguard
asked in Questions & Conversations

Exchange Oauth configuration documentation

Hi @Henk-Jan van Laar, it seems like the option to select the Exchange API has moved to a different tab.Starting from step 6, the following might work: Select Add a permission. On the Request API permissions page, go to the tab APIs my organization uses, search for Office and select Office 365 Exchange Online. Select Delegated permissions and then select EWS.AccessAsUser.All under EWS. Click on Add permissions. If it still does not work, it might be required to replace the assigned Delegated permissions with the Application permission full_access_as_app under Other permissions.The documentation will be updated if this solution works.

3
H
Vanguard
1 year ago
L
Moderator
Leon Kroon
published in News & Blogs

Introducing the Thinkwise Container RegistryBlog

Hi @Arie V, the configuration for both Indicium and the Universal GUI can be fully customized by providing environment variables to the container, with support to pass custom JSON to the container as configuration. This gives the ability to modify the configuration of the container depending on the environment it runs in, without customizing it before deploying it.In addition to this, it is also possible to simply mount the configuration file (appsettings.json and config.json) inside the container, but I think this approach makes the containers less flexible.As for the custom CSS and files for the Universal GUI, these can be mounted inside the container as well.It is not possible to modify the web.config of Indicium inside the container yet. Are these settings still mandatory inside a container, and if so, could these settings be provided with environment variables too?Full documentation for the container images will be published soon. One of the things I intend to solve with this regi

47311
Freddy
1 year ago

Badges

Show all badges
Terms & ConditionsCookie settings