dudeswave2/dudeswave/ebin/dudeswave.app

{application,dudeswave,
             [{description,"The dudeswave web experience"},
              {vsn,"1.0.0"},
              {modules,[dudeswave,dudeswave_app,dudeswave_handler,
                  dudeswave_user_handler,dudeswave_supervisor,
                  dudeswave_auth,dudeswave_auth_handler]},
              {registered,[]},
              {applications,[kernel,stdlib,erts,cowboy,ranch]},
              {mod,{dudeswave_app,[]}},
              {env, [
                  {ip,"127.0.0.1"},
                  {port,8080},
              ]},
              {start_phases,[]}]}.
Import the initial dudeswave code. At this point it handles only GETs, giving back plain text responses in case of errors. The intention is to also produce some static pages for those, where the CSS we will chose applies. Other APIs will be managed through their respective handlers, whose routes will be setup before this one. 2024-07-23 15:52:57 -05:00			`{application,dudeswave,`
			`[{description,"The dudeswave web experience"},`
			`{vsn,"1.0.0"},`
Enter the user handler API. For now it handles PUTs, to create new users. It's still a partial implementation and there is no documentation yet. POST, PATCH and DELETE will arrive later to handle other users operations. 2024-07-26 18:57:34 -05:00			`{modules,[dudeswave,dudeswave_app,dudeswave_handler,`
Complete the registration API. After some fight to decide on the right design, we finally have a module to handle users details. The API is JSON-based and it's documented on the top of the dudeswave_handler.erl file. The dudeswave_auth module, implements the functions that handle things at the storage layer, as we would like to reuse those capabilties in the future. To add, the "delete" call doesn't handle removing the cookies for the moment, It'll come with the next commit. Additionally, after that, a related test suite will be added, in order to start to test the whole thing locally. 2024-08-06 18:17:35 -05:00			`dudeswave_user_handler,dudeswave_supervisor,`
Introduce the authentication handler. The user handler will also receive the ability to answer with JSON bodies soon. 2024-08-09 17:19:17 -05:00			`dudeswave_auth,dudeswave_auth_handler]},`
Import the initial dudeswave code. At this point it handles only GETs, giving back plain text responses in case of errors. The intention is to also produce some static pages for those, where the CSS we will chose applies. Other APIs will be managed through their respective handlers, whose routes will be setup before this one. 2024-07-23 15:52:57 -05:00			`{registered,[]},`
			`{applications,[kernel,stdlib,erts,cowboy,ranch]},`
			`{mod,{dudeswave_app,[]}},`
			`{env, [`
			`{ip,"127.0.0.1"},`
			`{port,8080},`
			`]},`
			`{start_phases,[]}]}.`