... | ... | @@ -23,44 +23,13 @@ Regardless of CMS debates, it seems like a good time to bring CiviCRM Standalone |
|
|
|
|
|
Don't worry! Having CMS integrations will always be what makes CiviCRM standout compared to other solutions. CiviCRM must be a good fit for small organizations with limited technical and financial means, and also be a good fit as we help those organizations grow.
|
|
|
|
|
|
# Todo
|
|
|
|
|
|
* Installer
|
|
|
* Login page (and/or login via Oauth, but we should have something easy to use)
|
|
|
* Password reset
|
|
|
* 2fa support (via extension?)
|
|
|
* Manage users -> Setting a password for a Contact - Standalone had something
|
|
|
* Manage roles/permissions (re-use what WordPress has? or Standalone?)
|
|
|
* Basic theme for frontend pages?
|
|
|
|
|
|
Things to consider:
|
|
|
|
|
|
* Translation / multi-lingual (lcMessages would be fine)
|
|
|
* Installation documentation, visibility on civicrm.org/download
|
|
|
|
|
|
## Need help
|
|
|
|
|
|
* [x] How do we get the CSS/JS assets to be loaded in the HEAD? (c.f. templates/CRM/common/standalone.tpl)
|
|
|
* [ ] Get the CiviCRM menu to display (something to do with how asset paths are resolved?)
|
|
|
* [x] CiviCRM dashboard has an AngularJS error (was missing `vendor/civicrm-core/bower_components`, but seems OK on latest composer builds)
|
|
|
* [ ] On the `/civicrm/admin` page, the links are missing the leading `/`
|
|
|
* [ ] Session handling? user management?
|
|
|
* [x] Making clean URLs work? (c.f. web/index.php, `$_SERVER['REQUEST_URI']`)
|
|
|
* [ ] How to launch the installer? (edit: maybe it "just works", but I was testing with an existing database, need to re-test with a new DB)
|
|
|
Proof of concept of CiviCRM Standalone, as of 2021-12-15:
|
|
|
|
|
|
![image](uploads/b752f3f73c0f628961e6846407cd9dbe/image.png)
|
|
|
|
|
|
# Tooling
|
|
|
|
|
|
* [ ] buildkit support
|
|
|
* [ ] cv support
|
|
|
* [ ] tar.gz release builder
|
|
|
* [ ] demo site
|
|
|
|
|
|
# Random
|
|
|
# Todo
|
|
|
|
|
|
* Github repo civicrm-standalone, that we could build using composer (require civicrm-core, civicrm-setup, etc), and distribute on c.o as a tar.gz.
|
|
|
* Login feature could be an extension, and could be disabled if people want to use something else such as Oauth SSO or LDAP.
|
|
|
https://lab.civicrm.org/dev/core/-/issues/2998
|
|
|
|
|
|
# Manual installation
|
|
|
|
... | ... | |