-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/configurable #343
Feature/configurable #343
Conversation
* Create new branch tracking iNZightVIT/Lite2 changes * fix conflicts * modes? * ui fix * fix import * fix lite2 env variable * prevent dataset to show before confirm * fix url import * remove comments * fix rdata data selection bug * fix(server): LITE_ -> CAS_; bug in decryption code; import wkb, openssl - Replace LITE_ with CAS_ (for now) given this is still a hard-coded solution - fix parentheses in the raw2char / aes_cbc_decrypt logic - remove wkb code and just import the wkb package (minimal overhead) - remove library calls, use namespacing instead (openssl, wkb) * wrap LITE2 if * add function sample_if_lite2 * fix lite2 UI * fix datetime --------- Co-authored-by: Charco Hui <phui285@gmail.com>
It seems that row.names() and colnames() are triggering the reload, and by refactoring slightly the loading-loop seems to go away.
This PR is being deployed to Railway 🚅 Lite: ◻️ REMOVED |
Store config as an unaltered list; display version info on landing page. Minor refactor of some parameter handling.
Configuration (at least on Railway) is not user-session specific, and instead affects the entire instance. Can we try hacking into the |
Store LITE_VERSION and LITE_CONFIG in the session$userData object
Using session seems to work consistently. However, since To do:
|
No description provided.