|
Grex > Agora > #59: Recommendations for Database Engine/backend | |
|
| Author |
Message |
| 12 new of 21 responses total. |
papa
|
|
response 10 of 21:
| 
Oct 13 22:52 UTC 2020 |
resp:9 Amen!
|
tod
|
|
response 11 of 21:
|
Oct 14 18:25 UTC 2020 |
re #9
The name of the bar was Zebra. You deciphered the bar code! As it was
revealed in John 2
|
walkman
|
|
response 12 of 21:
|
Oct 17 21:13 UTC 2020 |
Q said it first
|
tod
|
|
response 13 of 21:
|
Oct 19 00:49 UTC 2020 |
TheGrinchWhoStoleDuringProtests
|
gelinas
|
|
response 14 of 21:
|
Oct 21 11:59 UTC 2020 |
To close the loop, I've decided against trying to write my own database
application to catalog my library.
I found Delicious Library, version 3, by Delicious Monster
(delicious-monster.com) that will do what I want. It's not free, but $38.99
isn't bad.
|
cross
|
|
response 15 of 21:
|
Nov 23 15:40 UTC 2020 |
PostgreSQL is good, but for the sorts of things you're talking about,
it seems like SQLite would be just fine.
|
walkman
|
|
response 16 of 21:
|
Nov 25 16:21 UTC 2020 |
I have a question about apache2 redirects.
I have a wordpress install which is in:
/usr/share/wordpress
My apache2 redirect (/var/www/html/.htaccess) looks like this:
Redirect / http://domain.com/blog
This effectively redirects the apache2 to the /usr/share/wordpress
directory.
However, I also have Nextcloud installed in /var/www/html/nextcloud.
Is there a way to have (2) redirects?
One for domain.com/blog (the wordpress install /usr/share/wordpress)
and
One for domain.com/nextcloud (the nextcloud install
/var/www/html/nextcloud)
If this is possible, what would the .htaccess file look like and are
there other steps?
Thanks in advance!
|
tod
|
|
response 17 of 21:
|
Nov 29 19:52 UTC 2020 |
Create a file for each site in
/etc/apache2/sites-available by copying 000-default.conf
modify those
then activate the new conf files
(This assumes you're using different domain names for each one?)
to activate the new conf files use the a2ensite command
then restart apache2
|
walkman
|
|
response 18 of 21:
|
Nov 29 22:10 UTC 2020 |
the problem is this:
the root domain has an alias "/blog"
I think this is messing up the nextcloud alias.
So the server does this after i enable the nextcloud.conf, enable it and
restart apache2:
type in the address in the web browser:
https://domain.com/nextcloud
this is what it does:
https://domain.com/blogblogblogblogblogblogblogblogblogblognextcloud/
The page isn t redirecting properly
An error occurred during a connection to domain.com
------
and if i enter this:
https://domain.com/blog/nextcloud
I get an internal server error.
------
Alias /nextcloud "/var/www/html/nextcloud/"
<Directory /var/www/html/nextcloud/>
Options +FollowSymlinks
AllowOverride All
<IfModule mod_dav.c>
Dav off
</IfModule>
SetEnv HOME /usr/share/wordpress/nextcloud
SetEnv HTTP_HOME /usr/share/wordpress/nextcloud
</Directory>
---------------
I think the only way to fix this is to move the wordpress to
/var/www/html and not have a "/blog" alias.
|
tod
|
|
response 19 of 21:
|
Dec 1 03:47 UTC 2020 |
I agree - put webserver root under html
|
walkman
|
|
response 20 of 21:
|
Dec 1 17:29 UTC 2020 |
I appreciate your help on this!
|
walkman
|
|
response 21 of 21:
|
Dec 1 18:23 UTC 2020 |
I just did it - it works now. Not sure why the install of wordpress
would go into /usr/share/wordpress to begin with but it seems to be
working fine. There's no executable component to wordpress - just plain
text files. Easy to back up... I didn't like the idea of using an alias
anyway.
|