forked from projects/fipamo
ro
252059df19
turned on the abiity to save settings to config file via the settings page the current member session needs to updated by the data coming in but that will be handled by a specific member service that hasn't been built yet, so just commenting it out for now also fixed a minor bug that was stopping the save on render toggle from working correctly, so now it's saving and updating the status properly now
30 lines
1.1 KiB
PHP
30 lines
1.1 KiB
PHP
<?php
|
|
|
|
use Illuminate\Support\Facades\Route;
|
|
use App\Http\Controllers\API\AuthAPIController;
|
|
use App\Http\Controllers\API\PageAPIController;
|
|
use App\Http\Controllers\API\FileUploadAPIController;
|
|
use App\Http\Controllers\API\SettingsAPIController;
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| API Routes
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here is where you can register API routes for your application. These
|
|
| routes are loaded by the RouteServiceProvider and all of them will
|
|
| be assigned to the "api" middleware group. Make something great!
|
|
|
|
|
*/
|
|
|
|
//check if session is active
|
|
Route::get("/v1/status", [AuthAPIController::class, 'status']);
|
|
//handle page editing actions
|
|
Route::put("/v1/page/write", [PageAPIController::class, 'write']);
|
|
Route::post("/v1/page/create", [PageAPIController::class, 'create']);
|
|
//handle file uploads
|
|
Route::post("/v1/files", [FileUploadAPIController::class, 'upload']);
|
|
//settings
|
|
Route::put("/v1/settings/publish", [SettingsAPIController::class, 'publish']);
|
|
Route::put("/v1/settings/sync", [SettingsAPIController::class, 'sync']);
|