Closed caronc closed 6 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 99.28%. Comparing base (
26d8e45
) to head (ce5ffcd
). Report is 3 commits behind head on master.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
̶G̶e̶t̶t̶i̶n̶g̶ ̶a̶n̶ ̶e̶r̶r̶o̶r̶ ̶w̶h̶e̶n̶ ̶t̶r̶y̶i̶n̶g̶ ̶t̶o̶ ̶u̶s̶e̶ ̶̶l̶u̶n̶a̶s̶e̶a̶
̶.̶.̶.̶.̶ ̶B̶a̶d̶ ̶A̶t̶t̶a̶c̶h̶m̶e̶n̶t̶
Yup... was using wrong container for this repo....
Are you using my Docker container or LinuxServer.io?
updated... was struggling getting Lunasea to work... finally figured it out... your container definitely works better
LinuxServer.io is a great solution, but attachments are disabled out of the gate. I think i may need to still investigate why simple notifications aren't working with it in this state.
Description:
Related issue (if applicable): #1070
Syntax
Valid syntax is as follows:
Cloud Hosting
lunasea://{toFireBaseUser}
lunasea://{toFireBaseUser1}/{toFireBaseUser2}/{toFireBaseUserN}
lunasea://+{toFireBaseDevice}
lunasea://+{toFireBaseDevice1}/{toFireBaseDevice2}/{toFireBaseDeviceN}
You can mix and match as well:
lunasea://{user}:{pass}@/+{toFireBaseUser1}/{toFireBaseDevice1}/
Private Hosting This works the exact same way; you can just additionally specify your connection details to your local server:
lunasea://{user}:{pass}@{hostname}/{toFireBaseUser}
lunasea://{user}:{pass}@{hostname}/{toFireBaseUser1}/{toFireBaseUser2}/{toFireBaseUserN}
lunasea://{user}:{pass}@{hostname}/+{toFireBaseDevice}
lunasea://{user}:{pass}@{hostname}//+{toFireBaseDevice1}/{toFireBaseDevice2}/{toFireBaseDeviceN}
lunasea://{user}:{pass}@{hostname}:{port}/{toFireBaseUser}
lunasea://{user}:{pass}@{hostname}:{port}/{toFireBaseUser1}/{toFireBaseUser2}/{toFireBaseUserN}
lunasea://{user}:{pass}@{hostname}:{port}/+{toFireBaseDevice}
lunasea://{user}:{pass}@{hostname}:{port}//+{toFireBaseDevice1}/{toFireBaseDevice2}/{toFireBaseDeviceN}
You can mix and match as well:
lunasea://{user}:{pass}@{hostname}/+{toFireBaseUser1}/{toFireBaseDevice1}/
lunasea://{user}:{pass}@{hostname}:{port}/+{toFireBaseUser1}/{toFireBaseDevice1}/
Use
lunaseas://
for a Secure (https://
) connection andlunasea://
for Insecure (http://
).lsea://
andlseas://
can also be used as an alias tolunasee://
andlunaseas://
(respectively) if you choose.Parameter Breakdown
no
.cloud
andprivate
. This is detected if no otherwise specified. When set toprivate
, a hostname must be provided as part of the URL. When set tocloud
, all elements are presumed to be notification end points and https://lunasea.app is used. In cloud mode, all transactions are secure (regardless if you specifylunasea://
orlsea://
).New Service Completion Status
%global common_description
Checklist
flake8
)Testing
Anyone can help test this source code as follows: