mirror of
https://github.com/dalbodeule/snap-admin.git
synced 2025-08-07 12:41:11 +00:00
Renamed dbadmin references to snapadmin (#29)
This commit is contained in:
@@ -96,25 +96,25 @@
|
||||
|
||||
<pre>
|
||||
<code class="language-properties">## The first-level part of the URL path: http://localhost:8080/${baseUrl}/
|
||||
dbadmin.baseUrl=admin
|
||||
snapadmin.baseUrl=admin
|
||||
|
||||
## The package(s) that contain your @Entity classes
|
||||
## accepts multiple comma separated values
|
||||
dbadmin.modelsPackage=your.models.package,your.second.models.package
|
||||
snapadmin.modelsPackage=your.models.package,your.second.models.package
|
||||
|
||||
## At the moment, it's required to have open-in-view set to true.
|
||||
# spring.jpa.open-in-view=true
|
||||
|
||||
## OPTIONAL PARAMETERS
|
||||
## Whether to enable SnapAdmin
|
||||
# dbadmin.enabled=true
|
||||
# snapadmin.enabled=true
|
||||
#
|
||||
## Set to true if you need to run the tests, as it will customize
|
||||
## the database configuration for the internal DataSource
|
||||
# dbadmin.testMode=false
|
||||
# snapadmin.testMode=false
|
||||
#
|
||||
## SQL console enable/disable (true by default)
|
||||
# dbadmin.sqlConsoleEnabled=false
|
||||
# snapadmin.sqlConsoleEnabled=false
|
||||
</code>
|
||||
</pre>
|
||||
|
||||
@@ -344,11 +344,11 @@ public class Payment { ... }</code>
|
||||
<div class="separator"></div>
|
||||
|
||||
<h3 id="settings-panel">3.2 The Settings panel</h3>
|
||||
<p>As mentioned earlier, the Settings panel primarily provides options to customize the branding/appearance of the web interface. These settings are persistent across restarts and are stored in an embedded H2 database (file named <code>dbadmin_internal</code>), along with other data required by SnapAdmin.</p>
|
||||
<p>As mentioned earlier, the Settings panel primarily provides options to customize the branding/appearance of the web interface. These settings are persistent across restarts and are stored in an embedded H2 database (file named <code>snapadmin_internal</code>), along with other data required by SnapAdmin.</p>
|
||||
|
||||
<h2 id="security">4. Security</h2>
|
||||
<p>SnapAdmin does not implement authentication and/or authorization mechanisms. However, you can use a standard Spring security configuration in order to limit access to the web UI or specific parts of it.</p>
|
||||
<p>All SnapAdmin routes start with the value of <code>dbadmin.baseUrl</code> property, and all write operations (edit, create, delete) are implemented as <code>POST</code> calls. The following code provides an example security configuration (assuming SnapAdmin runs at <code>/admin</code>):</p>
|
||||
<p>All SnapAdmin routes start with the value of <code>snapadmin.baseUrl</code> property, and all write operations (edit, create, delete) are implemented as <code>POST</code> calls. The following code provides an example security configuration (assuming SnapAdmin runs at <code>/admin</code>):</p>
|
||||
|
||||
|
||||
<pre>
|
||||
|
@@ -110,10 +110,10 @@
|
||||
<p>Add the minimum required properties to your <code>application.properties</code> file.</p>
|
||||
<pre>
|
||||
<code class="language-properties"># the root path of all SnapAdmin routes
|
||||
dbadmin.baseUrl=admin
|
||||
snapadmin.baseUrl=admin
|
||||
|
||||
# comma-separated list of packages to scan for @Entity classes
|
||||
dbadmin.modelsPackage=your.models.package
|
||||
snapadmin.modelsPackage=your.models.package
|
||||
</code>
|
||||
</pre>
|
||||
</div>
|
||||
|
Reference in New Issue
Block a user