question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[FEAT] define ini file path

See original GitHub issue

Is your feature request related to a problem? Please describe. i have two Philips Android TVs and want to monitor them from my Docker Container https://github.com/b2un0/pylips/blob/master/Dockerfile

but i can’t define a absolute path of the settings.ini, so i must mount them from outside.

Describe the solution you’d like an new argument to define a path of the settings.ini

Describe alternatives you’ve considered mount the settings.ini file absolute like the following is not an option for me:

docker run -d \
    --name pylips-70PUS7304 \
    --restart=unless-stopped \
    -v ~/pylips_70PUS7304.ini:/opt/pylips/settings.ini \
     b2un0/pylips:latest

Additional context

i wish i could something like this where pylips_data is an named docker volume which contained the following files:

$ pwd 
/var/lib/docker/volumes/pylips_data
$ tree
└── _data
    ├── 55PUS6551.ini
    └── 70PUS7304.ini

1 directory, 2 files

and i can run both container with the same volume:

docker run -d \
    --name pylips-70PUS7304 \
    --restart=unless-stopped \
    -v pylips_data:/mnt/pylips_data/ \
     --entrypoint "python /opt/pylips/pylips.py --ini /mnt/pylips_data/70PUS7304.ini" \
     b2un0/pylips:latest
docker run -d \
    --name pylips-55PUS6551 \
    --restart=unless-stopped \
    -v pylips_data:/mnt/pylips_data/ \
     --entrypoint "python /opt/pylips/pylips.py --ini /mnt/pylips_data/55PUS6551.ini" \
     b2un0/pylips:latest

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
eslavnovcommented, Nov 27, 2019

Hey, @b2un0!

Better late than never: the new version should support custom config paths, use it like this:

python pylips.py --config '/home/eslavnov/repos/Pylips/some_settings.ini'

I’ve run some tests and it seems to be working fine, but it could be that I’ve missed something - please let me know if it works for you. Thanks!

1reaction
eslavnovcommented, Nov 20, 2019

Hey @b2un0,

Terribly sorry for the delay: I had to deal with some personal stuff and had zero time to work on Pylips. I will fix this issue by the end of this week.

Sorry again!

Read more comments on GitHub >

github_iconTop Results From Across the Web

9 futuretense.ini - Oracle Help Center
The futuretense.ini file is the main property file for WebCenter Sites. ... server (iAS); the path is defined to be the path used...
Read more >
INI Files | Working with Files in Visual Basic - InformIT
Learn how to accomplish file operations easily by using Visual Basic code in this selection from Brian Siler and Jeff Spotts' book, ...
Read more >
puppetlabs/inifile - Puppet Forge
An arbitrary name used as the identity of the resource. path. The ini file Puppet will ensure contains the specified setting. provider. The...
Read more >
The Initialization File: BESA.ini
For the network administrator. This can be set to a path on the local network to the BESA update files, so that users...
Read more >
Putting PEARs php_dir into include_path in php.ini
As you may have already discovered, you need to set the PHP path configuration directive, 'include_path', in your system's php.ini file to:
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found