Bedework Schema files

[nileshkale]

We are trying to install Bedework on Postgresql. Are there standard scripts/schema files and any initial data available that can be used to setup the database?

[nileshkale]

The cli commands at http://bedework.github.io/bedework/#_setting_up_databases are only for CalendarDS. What about notifyDS, eventDS, syncDS and others. There seem to be only 3 scrips in CLI for schema?

[douglm]

I'll take a look. I have a script to restore things for testing which might be a better approach.

…

On 11/24/21 19:57, nileshkale wrote: The cli commands at http://bedework.github.io/bedework/#_setting_up_databases are only for CalendarDS. What about notifyDS, eventDS, syncDS and others. There seem to be only 3 scrips in CLI for schema? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW2MBXUYZQ7HL5GBIVKLWDUNWCXRANCNFSM5ITGJ3NQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nileshkale]

Is this script(s) available on GitHub?

[douglm]

On 11/25/21 14:03, nileshkale wrote: Is this script(s) available on GitHub?

Take a look in bedework/build/quickstart/linux/reset-pgQS.sh It references some data in the same repo. I'll take a look at creating the other schema files and update the script to restore them all. The bedework config files need to be changed to refer to the postgres dialect: look for <hibernateProperty>hibernate.dialect=org.hibernate.dialect.H2Dialect</hibernateProperty> and change them all to <hibernateProperty>hibernate.dialect=org.hibernate.dialect.PostgreSQL9Dialect</hibernateProperty> and the standalone.xml needs the datasources changed appropriately.

…

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW2MBSTRAMSYDPOX7YMCI3UN2CADANCNFSM5ITGJ3NQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nileshkale]

Thanks - I am assuming that changing hibernate dialect would not create the schema in the database? would still need the schema/DDL create files to create postgresQL schema?

[douglm]

On 12/2/21 09:41, nileshkale wrote: Thanks - I am assuming that changing hibernate dialect would not create the schema in the database? would still need the schema/DDL create files to create postgresQL schema?

Correct. You need to create the db first in psql and make the appropriate id the owner. You should be able to use the bw-cli utility to generate the schemas. I'd hoped by now I could have created you a set and posted them. However, I discovered my dev version is broken and I've been fixing it to do so - I'm working towards a release which upgrades to the latest wildfly and uses the wildfly module feature to make things more lightweight. I ended up with a whole bunch of hibernate issues which I think I've resolved. It might work for you with the last release. Take care with that - it looks like there's a bug and it tries to export it to the db whatever the setting of the "export" attribute.

…

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW2MBWVCPKLO52BBAYMOW3UO6AR5ANCNFSM5ITGJ3NQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nileshkale]

Hi - the bw-cli only some schemas, not all.
The cli commands at http://bedework.github.io/bedework/#_setting_up_databases are only for CalendarDS. What about notifyDS, eventDS, syncDS and others. There seem to be only 3 scrips in CLI for schema?
Is there a updated version of cli with other remaining schemas.

[nileshkale]

where can I find the CardDAV schema? Do not see it in JMX console to generate the option

[douglm]

Which version are you looking at?

…

On 12/7/21 18:32, nileshkale wrote: where can I find the CardDAV schema? Do not see it in JMX console to generate the option — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW2MBSCA2OUXWYSNTVEMP3UP2KQDANCNFSM5ITGJ3NQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nileshkale]

13.13.2 is what I am using but unable to see the cardDAV module in JMX to generate schema

[douglm]

Sorry for the delay. I'm working towards a new release and part of that work is to try to tidy this area up. It turns out I never implemented a carddav schema build - it's somewhat unfinished work. The carddav server is best thought of as a gateway service to other directory services - primarily ldap. When I set it up I don't generally set up the database part - at least for public events services. It does make sense to have somewhere to store contacts for personal address-books. I'll put it on my list to fix up

…

On 12/8/21 06:30, nileshkale wrote: 13.13.2 is what I am using but unable to see the cardDAV module in JMX to generate schema — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW2MBXBJ6GZYAGZHI5N3MLUP46WZANCNFSM5ITGJ3NQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.